Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. 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.

    Details

    • Workaround Description:
      Hide

      The current workaround I have is to add the follows property's:

                     <property name="org.jboss.osgi.system.modules.extra">
                          javax.jms.api
                      </property>
                      <property name="org.osgi.framework.system.packages.extra">
                          javax.jms;version=1.1
                      </property>
      
      Show
      The current workaround I have is to add the follows property's: <property name= "org.jboss.osgi.system.modules.extra" > javax.jms.api </property> <property name= "org.osgi.framework.system.packages.extra" > javax.jms;version=1.1 </property>

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  Aaron.Whiteside Aaron Whiteside
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: