Java Component Development: A Conceptual Framework
Subject:   Reinvent
Date:   2005-05-29 12:55:09
From:   PalashGhosh
Response to: Reinvent

Thanks for the comment.

This article talks more on concept rather than implementation.

There is no harm using Spring Framework and other open source framework readily available in the market.But we need to know what is there behind those Framework and how it suits in the organizaton where it's going to be used.If said organization is required to utilize only 40% advantages of Spring Framework,then probably we need to think twice before choosing the Spring framework as it has got its own learning curve and overhead of so many classes may not be used in said implementation.

The advantage of using home grown component has got some initial effort for conceptulization and design and development.But it would be(should be)
conceptualized considering the organizational need/requirement.But once it's done,it will be easy to use,maintain and enhance.

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Reinvent
    2005-07-21 04:44:57  kinko [View]

    Still seems like a reinvent to me. Spring and other frameworks really offer a way of utilizing IoC along interoperating with other open source libraries. You dont have to use the whole lot, take what you need, add what you need. You wouldnt advocate writing your own logging API so I am not sure why you advocate implementation of your own IoC. On the learning curve aspect, employees coming into a firm(plus current) will clearly of had more exposure to Spring and other open source products than your inbuilt container, hence I feel the learning time will be getting upto spead with your inhouse software.