[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:comment-tabpanel&focusedCommentId=12707119#comment-12707119 ] 

Thomas Diesler commented on AS7-2959:
-------------------------------------

Using external OSGi metadata should not be necessary any more. 
jboss-jms-api_1.1_spec-1.0.1.Final.jar already is a valid OSGi bundle.

It's package capabilities are correctly exported
{code}
22:08:51,494 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) Install resource: AbstractBundleRevisionAdaptor[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]
22:08:51,495 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4)    XIdentityCapability[atts={osgi.identity=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, type=osgi.bundle, version=1.0.1.Final},[anonymous]]
22:08:51,495 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4)    XResourceCapability[atts={osgi.wiring.bundle=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, bundle-version=1.0.1.Final},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
22:08:51,495 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4)    XHostCapability[atts={osgi.wiring.host=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, bundle-version=1.0.1.Final},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
22:08:51,495 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4)    XPackageCapability[atts={osgi.wiring.package=javax.jms, version=1.1},dirs={uses=javax.transaction.xa},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
22:08:51,495 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4)    XPackageRequirement[atts={osgi.wiring.package=javax.transaction.xa},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
{code}

This is derived from 

{code}
Bundle-Description: JSR-000914: Java(TM) Message Service (JMS) 1.1 API
Bundle-DocURL: http://www.jboss.org
Bundle-License: http://repository.jboss.org/licenses/cddl.txt, http://
 repository.jboss.org/licenses/gpl-2.0-ce.txt
Bundle-ManifestVersion: 2
Bundle-Name: Java(TM) Message Service (JMS) 1.1 API
Bundle-SymbolicName: org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec
Bundle-Vendor: JBoss by Red Hat
Bundle-Version: 1.0.1.Final
Export-Package: javax.jms;uses:="javax.transaction.xa";version="1.1"
Import-Package: javax.transaction.xa
{code}
                
> 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