[jboss-jira] [JBoss JIRA] (WFLY-1382) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

Thu May 23 12:15:07 EDT 2013

    [ https://issues.jboss.org/browse/WFLY-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776465#comment-12776465 ] 

Igor Shulika commented on WFLY-1382:
------------------------------------

Hi Thomas,
I have changed priority to "Critical" because it is very critical issue for our application. We are deploying multiple OSGi bundles with AOP Weaving by utilizing different start levels of the OSGi framework(order is very important).
Thanks!

> OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-1382
>                 URL: https://issues.jboss.org/browse/WFLY-1382
>             Project: WildFly
>          Issue Type: Bug
>          Components: OSGi
>    Affects Versions: 8.0.0.Alpha2
>            Reporter: Igor Shulika
>            Assignee: Thomas Diesler
>            Priority: Critical
>
> 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