To be more clear :-)
JCA never *starts* a transaction for you, it will merely enlist/delist a connection from
an *existing* transaction depending upon the type of connection manager in use.
NoTxConnectionManager -- no enlist/delist
TxConnectionManager (local and xa) enlist/delist depending upon transaction state at the
time of getConnection()
This is a typical assumption people make when coming from a straight JDBC environment.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969893#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...