Type: Feature Request
Resolution: Out of Date
Affects Version/s: None
Fix Version/s: None
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
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
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
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.