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
OK, finally I found the following solution:
Instead of adding the ActiveMQ resource adapter configuration to
standalone.xml, I added it to standalone-full.xml,
which seems to support MDBs. However you have the configure the connection
factory with a different name, because
otherwise it conficts
ar
\".*batch.environment is missing
[jboss.deployment.unit.\"TestAppEar.ear\".beanmanager*]"]}
On Tue, Feb 23, 2016 at 2:19 AM, THMayr wrote:
> Hi,
>
> I'm trying to integrate ActiveMQ 5.13.1 into WildFly 10.0.0 using the
> ActiveMQ reource adapter and a standal
Hi,
I'm trying to integrate ActiveMQ 5.13.1 into WildFly 10.0.0 using the
ActiveMQ reource adapter and a standalone ActiveMQ server. I configured the
reosoure adapter in WildFliy standalone.xml similar as described in the
posting
https://developer.jboss.org
Hi,
I'm trying to integrate ActiveMQ 5.13.1 into WildFly 10.0.0 using the
ActiveMQ reource adapter and a standalone ActiveMQ server. I configured the
reosoure adapter in WildFliy standalone.xml similar as described in the
posting
https://developer.jboss.org
