On the end, the XA separation didn't have anything to do with the transaction issue and JCA.
But... maybe http://jira.jboss.org/jira/browse/JBMESSAGING-945 still an issue.
Should we fix it or not?
We need to identify if there is any useCase for using JCA over non XA ConnectionFactories. The only one I can think of is connectionPool, as the user will be able to use ConnectionFactories directly.
Weston, any idea?