<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Folks,</div><div><br></div><div>currently we have a policy that server does not have a dependency on OSGi API and as a result on OSGiMetaData.</div><div><br></div><div>In several places we do a check like this</div><div><br></div><div><i>if (depUnit.hasAttachment(Attachments.OSGI_MANIFEST)) {</i></div><div><i> ...</i></div><div><i>}</i></div><div><br></div><div>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)</div><div>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.</div><div><br></div><div>I propose to move the OSGiMetaData one level up so that</div><div><br></div><div><i>if (depUnit.hasAttachment(Attachments.OSGI_METADATA)) {</i></div><div><i> ...</i></div><div><i>}</i></div><div><br></div><div>can be the deciding criteria. As a additional benefit web would no longer need to produce/consume the raw Manifest headers and OSGiMetaData would be treated like all other metadata structures.</div><div><br></div><div>cheers</div><div>--thomas</div><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></body></html>