Using JBoss 3.0 release. I have two session beans: one that is very simple, but has some basic business logic (EJB1).
The second session bean performs a database transaction (EJB2). The transaction tag in the descriptor for both beans is set to "Bean". We are using Oracle JDBC data source from the using a local transaction pool. We are not using Oracle's XA driver yet. Because the transaction is handled locally, the autoCommit() state for the connection in EJB2 is set to false. During EJB2's database transaction it makes a call to EJB1 to get a value. The call to EJB1 does not use the database at all during the call. BUT, when EJB2 returns from the call to EJB1, the autoCommit() is set back to true. Of course, this is a problem for the database transaction. Am I breaking the rules by calling another ejb method during a local database transaction? Thanks for any input! __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
