Yes, there is. Since you're not using transactions that are independent of the app server(and thus the app server doesn't know about the transaction at all, and isn't able to vote in it) the app server built in transactional support is not functional. An example:
EJB A: a SLSB EJB B: Your Entity Bean, PK=1. EJB C: Your Entity Bean, PK=2. If A, within a method, calls and modifies B and then C, and the calls on C produce an exception, B will be commited to the database. Where: EJB A: a SLSB EJB B: A correct Entity Bean, PK=1. EJB C: A correct Entity Bean, PK=2. If A, within a method, calls and modifies B and then C, and the calls on C produce an exception, the transaction will be rolled back. You should use either CMT or BMT in your BMP Entity Beans. Simply not coding transactions should do, the container would automatically handle the transactions (that's CMT). HTH, Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of Murali Mohan > Sent: Saturday, May 18, 2002 8:28 AM > To: [EMAIL PROTECTED] > Subject: Can I write JDBC Transactions in Bean managed entity Beans? > > > Hai, > > According to spec we must use declarative transactions for > entity beans. But I used JDBC transactions. It works fine. > > Is there any thing wrong? > > --Murali > > ============================================================== > ============= > 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". > >
