Currently in the 4.2 branch the | org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper | has been provided for two reasons: 1) We needed a way to override the isSameRM method to address a well known WebSphereMQ bug where mutliple XAResouces could not be enlisted in the same transaction from the same RM. Basically this simply amounted to moving the isSameRM stuff that was originally done for Oracle to be more generic. 2)Provide a serializable wrapper to support XA resource recovery using JBossTS. It was my plan to use this wrapper both on the inbound and outbound for JCA. From my understanding, this would enable JBossTS to reconsruct the XAResource and call recover as the XAResource (in this case the wrapper) would be written to the transaction log enabling JBossTS to do it's thing. I wanted to throw this out in the forum just be sure I am not missing anything and to solicit advice as to if this is the appropriate approach to take. The alternative approach would be to implement the | com.arjuna.ats.jta.recovery.XAResourceRecovery | interface and do things in the same manner as the JMS recovery work. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005906#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...