>I think it will be useful when we get to the point of redesigning the app >from scratch. It's a bit tough to replace the data access layer of a large >complex app that's been around for a long time though.
It is indeed difficult to change a long standing app but in the long run its a better approach. Definately something for the next major overhaul. I use the same design principals on all of my web apps. Even on my own custom written servers (non http). I am currently in my 7th year of continuous uptime with on average 10 structural app changes every month and i have to do that on 64 servers. Trust me when i say the technique works and is well worth investing the time to setup. Building the initial framework for it is a pain but once its up and running then its well worth it and you will never look back. 2008/9/18 Bill Davidson <[EMAIL PROTECTED]> > John5342 wrote: > >> I get around my the same kinds of problems by keeping all the layers of >> the >> web app seperate so that i can swap them out one at a time and create a >> near >> seemless upgrade. The layers in my web apps are: >> >> 1 The web interface. >> 2. The application logic. (this may itself be several layers in itself if >> the app is complicated) >> 3. The database access layer. >> 4. The database. >> >> [...] >> >> Hope what i said is useful. >> >> > > I think it will be useful when we get to the point of redesigning the app > from scratch. It's a bit tough to replace the data access layer of a large > complex app that's been around for a long time though. > > > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
