Hi, I you use JDBC you can use Container managed transaction, but in that case don't use setAutoCommit in java.sql.Connection.
You only have to declare in de deployment descriptor that the method "requires" transaction. -- Antoni Reus ----- Original Message ----- From: "pjaques" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 13, 2001 4:45 PM Subject: Transactions Hi, Everybody Thanks for all answer to my last question. But I think I was not very clear with my answer. I have a session bean that has bean managed transaction implemented with JDBC. This bean can keep the same transaction when it calls methods of others session beans? Is it possible? And another question? Is it possible that a session bean has container managed transaction with JDBC access?? If the bean use JDBC, it has bean managed transaction, ok? Thanks very much. Patricia __________________________________________________________________________ AcessoBOL, s� R$ 9,90! O menor pre�o do mercado! Assine j�! http://www.bol.com.br/acessobol ========================= 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". =========================================================================== 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".
