[jboss-jira] [JBoss JIRA] (AS7-2959) Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles.

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved AS7-2959.
---------------------------------

    Fix Version/s: 7.2.0.Alpha1
       Resolution: Done

    
> Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles.
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-2959
>                 URL: https://issues.jboss.org/browse/AS7-2959
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS, OSGi
>    Affects Versions: 7.1.0.Beta1
>            Reporter: Aaron Whiteside
>            Assignee: Jeff Mesnil
>            Priority: Minor
>             Fix For: 7.2.0.Alpha1
>
>
> Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles.
> I found however that adding <capability name="javax.xml.bind.api"/> worked as expected for the javax.xml.bind case (meaning it exposes the correct versions for the packages).
> It seems that <capability name="javax.jms.api"/> exposes a version of 0.0.0, which is obviously not 1.1.0 which is required by importers of javax.jms and thus bundles fail to deploy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira