Re: [jopr-dev] plugin classloader - child first?
I think that would probably work when running within the Agent. However,
I found that using the child-first classloader causes things to blow up
within embedded, because it causes errors when running within the
context of a webapp within JBossAS.
On 6/5/2009 3:11 PM, John Mazzitelli wrote:
What would blow up if our plugin classloaders were all always
child-first? Specificially, instances of our ChildFirstPluginClassLoader class?
I'm trying to see how I can make this stuff easier. And I'm thinkig - what if
there was no choice - the plugin classloader is always child-first so it will always try
to resolve classes using the plugin jars first, and only if the plugin cannot resolve them
will it go up to its parents?
_______________________________________________
jopr-dev mailing list
jopr-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jopr-dev