[
https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-667:
---------------------------------------
This is a conceptual issue that cannot get fixed easily. Subsystem capabilities are
considered to be part of the WildFly configuration - they are not deployments that go
through the chain of deployment unit processors (DUP) where the JavaEE integration
happens. WildFly does support persistent deployments. When you deploy
ejb-high-velocity-queue-mdb regularly, it should redeploy on server restart. The start
level can however not be associated with the deployment because of WFLY-1643. Please vote
on that issue.
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