[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.
4:59 p.m.
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: Clebert Suconic
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
11:39 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2959:
-------------------------------------
Assignee: Thomas Diesler (was: Clebert Suconic)
This auto-assigned to Clebert, but I suspect a person with OSGi expertise is a better
choice.
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: Thomas Diesler
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
3:05 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler resolved AS7-2959.
---------------------------------
Resolution: Rejected
You can specify OSGi metadata (i.e. package version) external of the jar. Have a look at
https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
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: Thomas Diesler
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
2:32 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reopened 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.
------------------------------------------------------------------------------------------------------------------------------------------------
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: Thomas Diesler
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
2:34 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reassigned AS7-2959:
-----------------------------------
Assignee: Clebert Suconic (was: Thomas Diesler)
Assigning back to Clebert, for a kind request to add the additional OSGi metadata as
described above.
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: Clebert Suconic
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
7:39 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil reassigned AS7-2959:
--------------------------------
Assignee: Jeff Mesnil (was: Clebert Suconic)
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
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
8:57 a.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-2959:
----------------------------------
@thomas, when I add the additional OSGi metadata to the javax.jms.api[1], the osgi
subsystem activates fine and it lists the javax.jms.api bundle as RESOLVED. However, the
version is 0.0.0 (instead of 1.1).
However, the javax.servlet.api also has its version set to 0.0.0 (instead of 3.0). I
suspect there is another issue related to the jbosgi-xservice.properties. Is it a known
issue?
{noformat}
[standalone@localhost:9999 subsystem=osgi] ./capability=javax.jms.api:add(startlevel=1)
{"outcome" => "success"}
[standalone@localhost:9999 subsystem=osgi] ./:activate
{"outcome" => "success"}
[standalone@localhost:9999 subsystem=osgi] ./:read-resource(include-runtime=true,
recursive=true)
{
"outcome" => "success",
"result" => {
"activation" => "lazy",
"startlevel" => 1,
"bundle" => {
"0" => {
"id" => 0L,
"location" => "System Bundle",
"startlevel" => 0,
"state" => "ACTIVE",
"symbolic-name" => "system.bundle",
"type" => "bundle",
"version" => "0.0.0"
},
"1" => {
"id" => 1L,
"location" => "javax.servlet.api:main",
"startlevel" => -1,
"state" => "RESOLVED",
"symbolic-name" => "javax.servlet.api",
"type" => "bundle",
"version" => "0.0.0"
},
"2" => {
"id" => 2L,
"location" => "javax.transaction.api:main",
"startlevel" => -1,
"state" => "RESOLVED",
"symbolic-name" => "javax.transaction.api",
"type" => "bundle",
"version" => "0.0.0"
},
"3" => {
"id" => 3L,
"location" => "javax.jms.api:main",
"startlevel" => -1,
"state" => "RESOLVED",
"symbolic-name" => "javax.jms.api",
"type" => "bundle",
"version" => "0.0.0"
},
"4" => {
"id" => 4L,
"location" => "org.osgi.enterprise",
"startlevel" => 1,
"state" => "RESOLVED",
"symbolic-name" => "osgi.enterprise",
"type" => "bundle",
"version" => "4.2.0.201003190513"
},
"5" => {
"id" => 5L,
"location" => "org.apache.felix.log",
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "org.apache.felix.log",
"type" => "bundle",
"version" => "1.0.0"
},
"6" => {
"id" => 6L,
"location" => "org.jboss.osgi.logging",
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "jboss-osgi-logging",
"type" => "bundle",
"version" => "1.0.0"
},
"7" => {
"id" => 7L,
"location" => "org.apache.felix.configadmin",
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "org.apache.felix.configadmin",
"type" => "bundle",
"version" => "1.2.8"
},
"8" => {
"id" => 8L,
"location" => "org.jboss.as.osgi.configadmin",
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "jboss-as-osgi-configadmin",
"type" => "bundle",
"version" => "7.2.0.Alpha1-SNAPSHOT"
}
},
"capability" => {
"javax.servlet.api" => {},
"javax.transaction.api" => {},
"org.apache.felix.log" => {"startlevel" =>
"1"},
"org.jboss.osgi.logging" => {"startlevel" =>
"1"},
"org.apache.felix.configadmin" => {"startlevel" =>
"1"},
"org.jboss.as.osgi.configadmin" => {"startlevel" =>
"1"},
"javax.jms.api" => {"startlevel" => 1}
},
"property" => {"org.osgi.framework.startlevel.beginning"
=> {"value" => "1"}}
}
}
[standalone@localhost:9999 subsystem=osgi]
{noformat}
[1]
https://github.com/jmesnil/jboss-as/blob/AS7-2959_OSGi_JMS_capability/bui...
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
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
3:13 p.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
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
3:13 p.m.
[
https://issues.jboss.org/browse/AS7-2959?page=com.atlassian.jira.plugin.s...
]
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
5027
days inactive
5252
days old
8 comments
4 participants
participants (4)
-
Aaron Whiteside (Created) (JIRA) -
Brian Stansberry (JIRA)
-
Jeff Mesnil (JIRA)
-
Thomas Diesler (JIRA)