Hi Adrian. Currently JBossMessaging doesn't have its own ResourceAdaptor as you know. JBossMessaging is being deploy in EAP as the default messaging provider together with the current JCA/JMS adaptor. This results in errors in the testsuite like JBPAPP-750. For AS-5.0 and EAP-4.3 I'll help the messaging team by providing the ResourceAdaptor as you describe - and later we should provide an optimized version using the internal API. Also we should use all your ideas from the jboss-jca project and in JIRA for a new implementation of the JCA specs for the next version of the AS. But if requirements for the EAP platform is only to use JBossMessaging for its messaging implementation we can go directly to the internal API implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142095#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...