[
https://issues.apache.org/jira/browse/SLING-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610503#action_12610503
]
Felix Meschberger commented on SLING-563:
-----------------------------------------
Using separate metadata is probably worse than using automatically generated
metadata. Such separate files tend to get out of sync rather quickly with
unforeseen consequences. I would _not_ do that.
In addition, you might to take a look at PAX URL wrap [1] ?
In addition, let me just state, that the OSGi headers are part of the API of
the packages to use. So ranting about not being willing to add manifest headers
is probably the same as ranting about not willing to use a required interface.
IMHO Dan completely misses the point of bundles and what is required for
bundles.
[1] http://wiki.ops4j.org/confluence/display/ops4j/Pax+URL+-+wrap
> Allow non-bundle jars to be loaded as bundles using external metadata
> ---------------------------------------------------------------------
>
> Key: SLING-563
> URL: https://issues.apache.org/jira/browse/SLING-563
> Project: Sling
> Issue Type: Wish
> Components: OSGi
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Just read Dan Diephouse's post at [1] and I like the idea of "bundleizing"
> existing jar files using separate metadata files, to be able to load them
> unmodified.
> There are certainly security issues in doing this, but in a secure
> environment it might make it much easier to use any jar as an OSGi bundle.
> [1] http://netzooid.com/blog/2008/07/02/osgi-is-a-pita-bundles/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
