[
http://issues.ops4j.org/browse/PAXWICKET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11840#action_11840
]
Ittay Dror commented on PAXWICKET-27:
-------------------------------------
i solved by creating a fragment like so:
Require-Bundle: <list of bundles with META-INF>
Fragment-Host: org.ops4j.pax.wicket.pax-wicket-service
Export-Package: *;partial=true;mandatory:=partial
this works fine for me.
i don't understand the logic of not providing this in pax-wicket-service,
having something is better than nothing, even if fragile. but maybe add this to
your documentation as a workaround for those that need it.
> the pax wicket bundle should import 'META-INF'
> ----------------------------------------------
>
> Key: PAXWICKET-27
> URL: http://issues.ops4j.org/browse/PAXWICKET-27
> Project: Pax Wicket
> Issue Type: Bug
> Reporter: Ittay Dror
> Assignee: Niclas Hedhman
>
> it is a common idiom for a library to allow other libraries to hook into it
> by providing some special file (usuall properties) in META-INF. these files
> are found by using the context class loader and they can then contain
> reference to classes in the plugin libraries.
> in pax wicket and jetty (pax web) setup, the context class loader is
> BundleClassLoader, which uses the pax wicket bundle to load
> classes/resources. since the bundle doesn't import 'META-INF', it will not
> find the resources in other libraries (assuming they export 'META-INF')
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
