The JCA/JMS adatper is *ready* to move from the experimental stage at this point. I wanted this for 4.2. The only real issue at this point is the lack of a management API for the JCA/JMS adapter. It would be easy to dummy something up in the manner of the JMSContainerInvoker allowing for JMX management that simply delegates to the underlying JMSActivation. The only problem I see with this is how to uniquely identify a listener deployment. Current the JMSContainerInvoker uses the listener/jndi name combination. Obviously we don't have this with the adapter and I am not all that sure that this is the right approach. Of course the JBossMessageEndpointFactory could pass this info along in the ActivationSpec, but something just seems wrong with this. Adding fuel to the fire is that there are two JBossMessageEndpointFactories: one for EJB3 and one for EJB2(X) deployments. We should probably combine these two and go with one approach. This is independent of the above issue. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012680#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...