[
http://issues.ops4j.org/browse/PAXWICKET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11819#action_11819
]
Ittay Dror commented on PAXWICKET-27:
-------------------------------------
why will the bundle be wired to just one exporter? AFAIK, if two bundles import
and export a package and a third bundle imports it, then that third bundle
will be wired to both other bundles (there's also a solution when the third
bundle requires the bundles by using the 'split' operator)
in my use case, both packages (the one that looks for files in META-INF and
the one that has a file there) are third party packages. i just add a manifest
file to make then into bundles. Is there a way to wire a bundle to the context
class loader so it will look in it when finding resources? i tried making the
bundle with the properties file a fragment of pax-wicket-service, but then its
classes are not found from the other bundle.
> 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
