This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, I am trying to understand the problem that EJBs solve. So far the best I've come up with is that they handle some of the system-level issues that a "distributed, scalable" application needs. However, this is so vague as to be useless. If this is a 50,000 ft view, I need a 10,000 ft view! Thanks
When I first looked at EJB I asked the same question. And reading Monson-Haefel's book was not especially conducive towards quickly understanding WTF EJBs are about. From my perspective it's all about transactions. No transactions, no EJB. EJB makes it easier to build a transactional application. The distributed, scalable, secure, reliable, etc. qualities are all likely to be needed in a transactional application... so you EJB containers give you those too. The most concise explanation of why EJB is useful is on page 35 of Ed Roman's "Enterprise Java Beans" where he shows pseudocode for an explicit middleware application, versus the implicit middleware approach used by EJBs (his book is a better intro than the O'Reilly book, in my opinion, although I keep both handy). It'll be interesting to hear from others who have a different perspective on EJBs...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com