On 4/13/11 7:39 PM, denstar wrote:
One thing which we "load ourselves" so to speak, that I was
assuming
was going to cause problems, is infinispan. If I try to load up
infinispan using our custom classloader, I get this:
Caused by: org.infinispan.config.ConfigurationException: Unable to
instantiate class org.infinispan.executors.DefaultExecutorFactory
at org.infinispan.util.Util.loadClass(Util.java:75)
at org.infinispan.util.Util.getInstance(Util.java:161)
at
org.infinispan.factories.NamedExecutorsFactory.buildAndConfigureExecutorService(NamedExecutorsFactory.java:84)
at
org.infinispan.factories.NamedExecutorsFactory.construct(NamedExecutorsFactory.java:38)
at
org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:318)
at
org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:254)
at
org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:843)
at
org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:228)
at
org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:185)
at
org.infinispan.factories.GlobalComponentRegistry.<init>(GlobalComponentRegistry.java:79)
... 37 more
Caused by: java.lang.ClassNotFoundException:
org.infinispan.executors.DefaultExecutorFactory from [Module
"deployment.railo-infinispan.war:main" from Service Module Loader]
This one is hard to say without knowing how your custom CL works.
However, that exception shows that the lookup was happening on the WAR's
CL, so your CL must be delegating.
--
Jason T. Greene
JBoss, a division of Red Hat