Galbreath, Mark wrote: > Check out http://shop.t-mobile.com dude - the entire site is a Struts + EJB > app. If your EJBs didn't scale, you did not know what you were doing. > > Mark >
I would also say that you pick right database tables to make entity beans in the first place. This is where the performance probably failed. You can make SessionBeans pass back RowSet, or HashSet or DataTransferMaps of the rows of the database table instead. Especially in a shopping web app. Other people have advocate JDO as a replacement for EntityBeans and I think this technology also works, but I am not sure if it is distributed or supports the type of transactions that J2EE / JTA fully endorses. Couple of books "EJB Design Patterns" F.Marinescu and Mr Grand "Java Enterprise Patterns" spring to mind. > -----Original Message----- > From: V. Cekvenich [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 7:26 AM > > They are hype marketed as such. Most newer developers try them, as I did > when I was new, but in production they did not scale, so we removed > them. On new sites I skip the writing them part, since people would > only remove them in production. (some management that take EJB to > production are so upset that they go to the cached .NET ADO, so I steer > my client's clear). > -- Peter Pilgrim +-----\ +-++----++----+ Java Technologist | | | || || | 'n' Shine | O | | || --+| ---+ /\ | ._ / | | \ \ | | / \ | | \ \ | |+-- || ---+ A new day /_ _\ "Up" | | | | | || || | is coming || +-+ +-+ +-++----++----+ <home page="http://www.xenonsoft.demon.co.uk/"; /> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
