> 7) Another advantage of EJB I heard was “transaction > management”. Why do I > need that? I can use JSP/JavaBean to issue all kinds of SQL > statements and > commit or rollback any transaction as needed. Why do I need EJB’s > “transaction management”?
I tend to agree with you on other points. You will need a transaction management if you have a distributed transaction, which means more than one database are involved (or database schema for that matter). In fact you can make a one phase transaction with regular JavaBean (better with Data Access Objects), but for true two-phase commit you will need EJB. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.458 / Virus Database: 257 - Release Date: 2/24/2003 ==========================================================================To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
