[
http://issues.ops4j.org/browse/PAXWICKET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11841#action_11841
]
Stuart McCulloch commented on PAXWICKET-27:
-------------------------------------------
The extender pattern effectively does the same thing, but is more dynamic - the
OSGi framework has various APIs that allow you to search through the list of
installed bundles, reading their manifests and querying their resources. FYI,
these are the same APIs that are used by Spring-DM and the dmServer to find web
resources.
So can you tell us your use-case (ie. the problem you're trying to solve)
rather than the specific change you want made, because it's very likely that we
can provide a solution that works for you and others. Then we can consider all
the options, not just one :)
> 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
