Sling
  1. Sling
  2. SLING-2103

Felix OSGI System Bundle is not providing WS Addressing

    Details

      Description

      this is a follow-up of FELIX-2073.
      the system bundle in felix does not export the package javax.xml.ws.wsaddressing, which is part of JDK 1.6.
      it has to be added to jre-1.6.properties as well (see attached patch).

      p.s. this was already discussed on the sling mailing list http://www.mail-archive.com/dev@sling.apache.org/msg03813.html

      1. 110816_SLING-2103_patch.patch
        8 kB
        Stefan Seifert
      2. 110615_SLING-2103_patch.patch
        0.4 kB
        Stefan Seifert

        Issue Links

          Activity

          Hide
          Felix Meschberger added a comment -

          And added to launchpad builder list and build reactor in Rev. 1201320

          Show
          Felix Meschberger added a comment - And added to launchpad builder list and build reactor in Rev. 1201320
          Hide
          Felix Meschberger added a comment -

          Created new system bundle extension fragment for WS APIs in Rev. 1201319

          Show
          Felix Meschberger added a comment - Created new system bundle extension fragment for WS APIs in Rev. 1201319
          Hide
          Felix Meschberger added a comment -

          Creating a WS system bundle fragment

          Show
          Felix Meschberger added a comment - Creating a WS system bundle fragment
          Hide
          Stefan Seifert added a comment -

          i tried this by adding a

          <Bundle-RequiredExecutionEnvironment>
          JavaSE-1.6
          </Bundle-RequiredExecutionEnvironment>

          to the JRE 1.6 system extension bundle manifest, but it does not seem to work.
          the bundle is installed on JRE 1.5 as well, and the additional packages are listed as exported, although they do not exist on JRE 1.5.
          perhaps this setting is not supported in felix for "fragment" bundles which provide system bundle extensions?

          Show
          Stefan Seifert added a comment - i tried this by adding a <Bundle-RequiredExecutionEnvironment> JavaSE-1.6 </Bundle-RequiredExecutionEnvironment> to the JRE 1.6 system extension bundle manifest, but it does not seem to work. the bundle is installed on JRE 1.5 as well, and the additional packages are listed as exported, although they do not exist on JRE 1.5. perhaps this setting is not supported in felix for "fragment" bundles which provide system bundle extensions?
          Hide
          Justin Edelson added a comment -

          Perhaps what we can do is to have a framework extension bundle for Java 1.5 XML libraries and another for the Java 1.6 XML libraries (just the delta between 1.5 and 1.6). Both will be included in the default bundle list for Sling. The 1.6 bundle will have a Bundle-RequireExecutionEnvironment header of JavaSE-1.6 so it won't install on a 1.5 VM.

          WDYT?

          Alternatively, we could just kill support for 1.5

          Show
          Justin Edelson added a comment - Perhaps what we can do is to have a framework extension bundle for Java 1.5 XML libraries and another for the Java 1.6 XML libraries (just the delta between 1.5 and 1.6). Both will be included in the default bundle list for Sling. The 1.6 bundle will have a Bundle-RequireExecutionEnvironment header of JavaSE-1.6 so it won't install on a 1.5 VM. WDYT? Alternatively, we could just kill support for 1.5
          Hide
          Stefan Seifert added a comment -

          attached is a first draft of such an bundle which can be installed additionally to support all XML apis of JRE 1.6:
          110816_SLING-2103_patch.patch

          but i'm not totally happy with this solution.
          for all other apis shipped with the JRE there is an auto-detection for JRE 1.5 vs. JRE 1.6, depending on the VM sling is running in.

          now this does no longer apply to the XML APIs, the sling application developer has to install the additional "XML APIs for JRE 1.6" bundle manually.

          do you see any chance to apply such an auto-detection for this framework extension bundles as well within the original "framework-extension-xml" bundle?

          Show
          Stefan Seifert added a comment - attached is a first draft of such an bundle which can be installed additionally to support all XML apis of JRE 1.6: 110816_ SLING-2103 _patch.patch but i'm not totally happy with this solution. for all other apis shipped with the JRE there is an auto-detection for JRE 1.5 vs. JRE 1.6, depending on the VM sling is running in. now this does no longer apply to the XML APIs, the sling application developer has to install the additional "XML APIs for JRE 1.6" bundle manually. do you see any chance to apply such an auto-detection for this framework extension bundles as well within the original "framework-extension-xml" bundle?
          Hide
          Felix Meschberger added a comment -

          As of SLING-2109 I removed the exports for the XML APIs from the default properties files and moved them into a separate system bundle extension fragment (which basically just exports the XML APIs available in Java 5.

          I think to fix this issue, we just would have to provide a bundle doing the same for the Java 6 XML APIs...

          Show
          Felix Meschberger added a comment - As of SLING-2109 I removed the exports for the XML APIs from the default properties files and moved them into a separate system bundle extension fragment (which basically just exports the XML APIs available in Java 5. I think to fix this issue, we just would have to provide a bundle doing the same for the Java 6 XML APIs...

            People

            • Assignee:
              Felix Meschberger
              Reporter:
              Stefan Seifert
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development