Right, but that's for the older version (AFS/StdServerSession) and is basically giving
a warning about using non XA. The JCA adapter simply assumes that if you are not using an
XAConnectionFactory, or you have chosen the madness option (ie BMT, CMT/NotSupported) that
the local API will be used solely to support redelivery.
However, the problem I see is that the interceptor will suspend the transaction prior to
onMessage being invoked in the case of BMT and NotSupported. As result, the DB work being
done is not going to effect the overall outcode of the Tx because the underlying XA
connection will never be enlisted.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026685#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...