If it did, we'd fall back to the exact behavior we actually want for Messaging, and it
already happens in JBossMQ.
Remember that the JCA layer has nothing to do with the decision to send the message
through, which is taken by SpyXAResourceManager in JBossMQ's case, and could be taken
by MessagingResourceManager in ours.
The JCA layer just (correctly) does not enslist the XAResource with an inexistent JTA
View the original post :
Reply to the post :