One update: You don't have to reference the ActiveMQ resource adapter from the EJB3 subsystem in the WildFly configuration file. This defines only the default messaging system used by WildFly, when no explicit message broker is defined in the deployment descriptor of the EJB application.
Instead I added the reference to the resource adapter in the WildFly specific deployment descriptor "jboss-ejb3.xml" as follows. See also jboss-ejb3.xml Reference <https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference> . -- View this message in context: http://activemq.2283324.n4.nabble.com/Integrate-ActiveMQ-5-13-1-into-WildFly-10-0-0-tp4708055p4708636.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
