This post originated from an RSS feed registered with Java Buzz
by Nanik.
Original Post: Growing into a framework
Feed Title: Nanik's Weblog
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: Java, J2EE, Open Source, Cafe and other
In my current project we are developing a common module for our application, basically the common module enable us to use navigational buttons, managing DB connection and all the small but important stuff that enable the application to run. One thing that I found maintainig this common module is that from a small but useful module it grows to having it's own life and transforming into a standalone framework.
The difficulty facing us is that even though the framework is useful it requires a dedicated person to really refactor and also test and retest it to make sure that it is bug free (you wish!) and not to break anything, and most important any changes or modification that is made to the core should not impact any modules that has been built and tested in the application server.
One weird thing we found today (we are using iPlanet) is that if we use a non-serializable object and put it into a session it will throw an exception, got to read on this and see whether this is really a standard either in the JSP/Servlet spec.
Previous Topic
