Makes sense. Bummer though. > From: "Hendrik Schreiber" <[EMAIL PROTECTED]> > Reply-To: "Research Triangle Java User's Group mailing > list."<[EMAIL PROTECTED]> > Date: Thu, 20 May 2004 10:08:50 -0400 > To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]> > Subject: Re: [Juglist] Remote deployment to WebsphereApplicationServer? > >> At the end of they day though >> you'll have to say "gee, after all of this mangling for bad performance, I >> could have refactored my legacy code." > > The legacy app is written with Oracle forms and stored procedures. Eventually > it might go away. But refactoring is pretty much impossible. And for now it is > simply really unwise to alienate all of the existing _paying_ customers, by > messing with it too much or taking it away while we can only offer a half done > Java solution. > > This is a big enterprise asset management system. Not just a tiny application > you can rewrite in a year or so. > > For the time being we simply have to put up with the constraints we are > facing. Once there is no legacy application using the database, we can move on > and develop smarter solutions. > > -hendrik > _______________________________________________ > Juglist mailing list > [EMAIL PROTECTED] > http://trijug.org/mailman/listinfo/juglist_trijug.org >
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
