For bean managed transaction, if there is no distributed transactions envoled and my database operations are in a single method with single phase transaction, the effect of using JTA/JTS and the effect of using JDBC level transaction (Connection.setAutoCommit(false)) are the same. Am I right? By the way, has anybody seen "enlist transaction error ..." on WebSphere with Oracle 8i XADataSource? Thanks in adance ...
<i><br />Sun Certified Programmer for Java 2 Platform (SCJP)<br />Sun Certified Developer for Java 2 Platform (SCJD)<br />Sun Certified Web Component Developer for Java2 Platform, Enterprise Edition (SCWCD)<br />Sun Certified Business Component Developer for Java2 Platform, Enterprise Edition (SCBCD)<br />Sun Certified Enterprise Architect for J2EE (SCEA)<br />IBM Certified Enterprise Developer, WebSphere Studio V5.0<br /></i>
Joined: Mar 23, 2001
I have the same problem, anyone could help please?
Go a little further, what if 2 BMTs' 2 methods are involved?
Thanks a lot James
Joined: Feb 17, 2005
There are several differences that could influence your design. One of the differences between JTA and JDBC is that JTA doesn't support nested transactions, while JDBC might do. Another difference is related to SFSB: in both cases the transactional context is retained during multiple client calls. If the connection is closed, JDBC will lose the association between the bean and transactional context; it won�t get lost with JTA though.