From: Toby A. <tob...@pe...> - 2001-06-07 20:53:13
|
On Thu, Jun 07, 2001 at 04:06:21PM -0400, David Esposito wrote: > I thought that UserTransaction is not accessible outside of the bean > context? I know in 2.3 beta it's available outside of the JVM even (there's > a whole seperate issue there .. ) ... but with 2.2, I thought that the only > way to give explicit transaction bounds outside of a bean is to use > TransactionManager? You're right. You still shouldn't mess with the transaction manager. I'm not familiar enough with the transaction management code to say what the difference between TransactionManager.begin and UserTransaction.begin is. What you might want to do is to print out what the current transaction is at various points, like after trans.begin() and inside your EJB methods. TransactionManager.getTransaction().toString() should be sufficient. > Both my EntityBeans are "Required" transaction attributes ... That should be fine. As long as they're not RequiresNew. I'm suspecting that this is some sort of problem with propagating the transaction from Tomcat to JBoss. If so, hopefully someone who understands how that's supposed to work will step in. Toby. |