In that case though you should almost definitely use Stateless session beans + Value Objects. Of course no matter what you do, your performance is going to suck given these constraints. Your performance has almost certainly nothing to do with JBoss (and to be fair any bad performance you get won't be Websphere's fault). Without any caching and using BMP you are going to drive the garbage collector "bonky" so definitely get the VM with the fastest most tunable garbage collector. 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."
-Andy > From: "Hendrik Schreiber" <[EMAIL PROTECTED]> > Reply-To: "Research Triangle Java User's Group mailing > list."<[EMAIL PROTECTED]> > Date: Wed, 19 May 2004 18:47:28 -0400 > To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]> > Subject: AW: [Juglist] Remote deployment to WebsphereApplicationServer? > >> NEVER use BMP if you care about performance. BMP is as Gavin >> said the other >> night, broken. If you HAVE to write your own DB code, go all the way with >> Session beans that make value objects. Don't bother with BMP, it >> only buys >> you Container Managed Transactions. > > I know. And I wholeheartedly agree. > > Unfortunately I am not the architect in this operation. > > Also, it has been decided on the political level a while ago that the > application needed to fully conform to the Sun Blueprint and therefore needed > to have entity beans. At the same time there is another legacy application > talking directly to the database, which makes caching unfeasable. > > Maybe it's good, I'm not the architect ;-) > > -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
