Rickard, agree with you 100%. Reading Monson-Haefel's book (have read editions 1 & 2) and Ed Roman's new book (read his oldie too). They're the better way to start out . The spec is even more important for vendors since they have to implement this stuff (how did you handle it with jBoss ?). But EJB is still messy....
Cheers eddie ============== At 10:35 PM 31/01/2002, you wrote: Eddie Fung wrote: - I agree with a lot of your comments. EJB seems unnecessarily complex and yeah the spec reads like a legal document. Hell it's 572 pages long !! Get a book on EJB then. There's quite a few good ones out there, and Mastering EJB 2nd Edition is one I'd highly recommend (see http://www.theserverside.com/books/masteringEJB/index.jsp for free download of the PDF version) - the deployment cycle is hopeless. You can speed things up by either setting up an Ant task to batch up your deployment but you still have to set all the attributes on the Deployment Descriptor. M$ would make this cleaner by just right mouse clicking an EJB and setting the properties tab. You'll pretty much get this with XDoclet, and the new XDoclet GUI will allow you to do it by pointing&clicking. The bottom line is the Sun have released a spec that's meant to be open. They've tried to set everything up using descriptors to be more flexible. Flexibility can cause complexity and it's up to vendors to make it easier. IMHO it's up to tool makers to make it easier. If tool vendor happens to be container vendor, that's fine, but not necessary. /Rickard -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
