[ 
http://issues.ops4j.org/browse/PAXWICKET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11818#action_11818
 ] 

Alin Dreghiciu commented on PAXWICKET-27:
-----------------------------------------

It is wrong to import META-INF. This because the bundle will be wired to just 
one exporter of that package. So, assuming that pax wicket will import META-INF 
and there are more bundles that exports it. The framework will wire pax wicket 
to just one package, not to both of the bundles that exports it. Case when the 
import is worthless as it will not satisfy your use case.
I do not know what is your exact use case but seems like a pattern for an 
extender that based on the fact that some info is available in META-INF (like 
properties files) it will react and do "something". To help with that you can 
use the pax swissbox package.

> 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

Reply via email to