> From: Price, Erik [mailto:[EMAIL PROTECTED]] > > If they are overkill for webapps, what sorts of situations would benefit > from them? > (Not asking rhetorically, I'm honestly curious about when to use EJB since > I know nothing about them.)
Applications which are very transaction-oriented will benefit from the convenience of declarative transactions - it's much easier to write applications that don't have to manage transactions by hand. This is a compelling reason to use Session EJBs. There are, IMHO, no compelling reasons to use Entity EJBs. Entities are poorly thought out and implemented even worse. You are much, much better off with any of the open-source O/R mechanisms (Hibernate, OJB, Torque) or just simply hand-coding your JDBC. We would all be better off if Sun would just give up on this lousy idea and let that part of the spec die out. Jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
