[
https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin...
]
Thomas Diesler moved WFLY-1382 to JBOSGI-667:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-667 (was: WFLY-1382)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: (was: 8.0.0.Alpha2)
Component/s: (was: OSGi)
OSGi: "Export-EJB" header is not supported to install/start
EJB3 bundle from repository
---------------------------------------------------------------------------------------
Key: JBOSGI-667
URL:
https://issues.jboss.org/browse/JBOSGI-667
Project: JBoss OSGi
Issue Type: Bug
Reporter: Igor Shulika
I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my
OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare
capability in the standalone-osgi.xml file.
Here is my capability configuration.
<capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0"
startlevel="4"/>
Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments"
directory the message driven bean starting successfully (see below).
INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven
bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira