|
Re: context class loader [message #708198 is a reply to message #708182] |
Tue, 02 August 2011 15:03 |
|
Do you mean that the third party library uses the context class loader for loading? If so it should be able to find the resources accessible by the synthetic context.
In other words the library should explicitly use the context class loader, since Java will not make use of it by default.
|
|
|
|
|
|
|
|
Re: context class loader [message #709088 is a reply to message #709004] |
Wed, 03 August 2011 13:46 |
|
The synthetic context is used for PAR or scoped plan. Virgo builds a synthetic bundle and sets its loader as context class loader for all artefacts in the scope.
What's the packaging you are using - is it a PAR or a plan? Do you have a web app inside the PAR/plan?
|
|
|
|
Re: context class loader [message #709807 is a reply to message #709121] |
Thu, 04 August 2011 10:24 |
|
The webapp classloader (CL) is set by Tomcat on request (as by spec). Therefore the synthetic thread context CL from the PAR is overwritten with the webapp one. There may be applications that rely on this behaviour so we can't do much in this direction.
One thing that comes to my mind is to add the needed import(s) to your webapp so the FactoryFinder can load the class from the webapp CL.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03840 seconds