Adrian, you're sounding too much like Mark Little.
setAutomCommit(false); does not change the transactional characteristics of the connection
because autoCommit is already false. There is no state change with the call. Since there
is no state change, then no error should be thrown. So you can ignore a
setAutoCommit(false) with no repurcutions.
The problem the user is having is that he wants to invoke thirdparty code that he cannot
control, with a JTA/JCA managed connection within a transaction. Because of your
interpretation of the spec, he cannot do this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067017#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...