Uploaded image for project: 'JBoss OSGi'
  1. JBoss OSGi
  2. JBOSGI-698

Provide access to OSGiMetaData for server, web, etc

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Resolved
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: wildfly
    • Labels:
      None

      Description

      Currently we have a policy that server does not have a dependency on OSGi API and as a result to OSGiMetaData.

      In several places we do a check like this

      if (depUnit.hasAttachment(Attachments.OSGI_MANIFEST)) {
        ...
      }
      

      This however implies that the Manifest is the only possible source of valid OSGi metadata. The OSGi webapp spec allows for metadata to be specified as part of a "webbundle://" URI (see AS7-6006)

      To make this work, the integration code currently generates a Manifest and later OSGiMetaData from it. The above code still works even if the deployment content does not have a Manifest.

      I propose to move the OSGiMetaData one level down so that

      if (depUnit.hasAttachment(Attachments.OSGI_METADATA)) {
        ...
      }
      

      is the deciding criteria. As a additional benefit web would no longer need to produce/consume the raw Manifest headers and OSGi metadata would be treated like all other metadata structures.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              thomas.diesler Thomas Diesler
              Archiver:
              samahaja Sagar Mahajan

                Dates

                Created:
                Updated:
                Resolved:
                Archived: