[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB

[weston.price@jboss.com]

This would be an unusual case as most JMS providers provide both a non XA and an optional XA CF to create the underlying connection. What I am reading is that JBM does not provide the former as a standalone CF option.

The problem is that on the JCA side of things there is no way to determine from the 'transacted' parameter whether or not XA or non XA is to be used being that with XA this flag is simply ignored. In other words, the value of that flag is irrelevant in detrmining what type of connection to use (XA or non XA) being that there is not enough contextual information to make that determination. The only way to really do this would be to add a 'useXA' or 'isXA' type flag to the adapter that when present, would completely override the instanceof check to determine if it's XA or not. I am reluctant to do this as this as this would be the only case with a JMS provider where it it is necessary.


JBM would be the only JMS provider I have seen to date where you could not deploy a non XA JMS resource. WebSphereMQ, TIBCO, ActiveMQ, JBossMQ etc provide XA as an option as this is the only behavior mandated by the spec where the XA is optional. 






View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039469#4039469

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039469