| ContextFinder and 'jar plugins' [message #436727] |
Thu, 15 September 2005 15:33 |
 John J. Franey
Messages: 55
Registered: July 2009 |
Member |
|
|
Do I have this right? Does anyone know how to work around it?
A calling plugin invokes a method on a called plugin which is a jar only plugin. To get a resource, the called plugin uses getContextLoader which returns ContextFinder. ContextFinder delegates to the calling plugin's classloader. The calling plugin's classloader doesn't have knowledge of the called plugin's classpath. So resources on the called plugin's classpath are not available to the called plugin in this call chain.
I would like the called plugin to have access to the resources that are on its classpath even though it uses getContextLoader.
For example, RequiredPlugin defines a resource in META-INF, and one of its methods uses getContextLoader().getReources("META-INF/*..") to load the resource. CallingPlugin invokes this method directly. Unless CallingPlugin has this resource on its classpath (like in its own META-INF directory), RequiredPlugin won't find it.
Thanks,
John
|
|
|
Powered by
FUDForum. Page generated in 0.05096 seconds
] 
Search
Help
Register
Login
Home
