Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-2109

Separate some system bundle provide packages into properties for easier overwrite

    XMLWordPrintableJSON

Details

    Description

      Currently a number of Java Extension packages are exported without a version from the system bundle; for example javax.transaction., or javax.xml,.

      The problem with these packages is that some applications will not want to depend on these packages from the environment hence do not want them to be exported from the system bundle. Yet, in different contexts like the default Sling Launchpad build, we just want them available.

      To fix this issue, the following should be done:

      • Remove Activation, Transaction, and XML APIs from the System Bundle Export
      • Create two system extension fragment bundles: (1) for JTA and (2) for XML APIs

      The javax.activation API is problematic anyway and should probably not be used from the environment due to the extension loading mechanism employed by default. The JTA and XML API system extension fragment bundles can be replaced by real bundles. For example to use JAT inside the OSGi framework the Apache Aries Transaction Manager bundle can be deployed instead of the JTA system extension fragment.

      This is related to SLING-1958 which is about replacing the XML related exports from the system with bundles embedding the API in the framework itself and thus encapsulating from the environment.

      Attachments

        Issue Links

          Activity

            People

              fmeschbe Felix Meschberger
              fmeschbe Felix Meschberger
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: