Have you got your answer for this question?
Have you try to use ActiveMQ resource adaptor to connect to ActiveMQ running separately from JBoss 5.1? I am keep getting the following runtime exception when start up JBoss 5.1 instance, the same configruation works just fine in JBoss 4.2.2GA:
Caused by: java.lang.RuntimeException: Unable to choose messagingType interface for MDB AuditService from 
Also, were you able to use JNDI name for inbound queue with ActiveMQ? I have to specify the physical Queue name inside my MDB for inbound message, but prefer to use jndi name in my code and configure the jndi name in adminobject inside activemq-jms-ds.xml file. How did you get around tis?
Alexander Petitjean wrote:
I am confused - because JBoss Messaging is (as far as i know) also embedded via JCA and also bound to global JNDI and - I can successfully lookup the JBoss Messaging ConnectionFactory from a client outside !!! Why does it work - is this bug a feature ? ;-)
Thx so far !
This is an FAQ.
The JCA ConnectionFactorys are pools for local use bound in the java:/ namespace which is not accesible remotely.
JBoss Messaging provides a different ConnectionFactory for remote client usage.
For what ActiveMQ provides, you'll need to ask them.
Whatever it is, it needs to be bound in the global namespace, not java:/