-
1. Re: Class loader isolation for WAR
alesj Jan 20, 2012 5:19 AM (in response to yvsailaja)I've seen this issue before, at least this weird resource with 1.0 at the start. Check how it was dealt before.
But I guess you could ignore this exception by adding to IgnoreSetErrorHandler's set of ignored exceptions -- check where IgnoreSerErrorHandler is defined in -jboss-beans.xml file.
-
2. Re: Class loader isolation for WAR
alesj Jan 20, 2012 5:20 AM (in response to yvsailaja)for .war, child-first delegation should already work. But it depends how it's used, as you can see, it's not bullet proof.
-
3. Re: Class loader isolation for WAR
yvsailaja Jan 20, 2012 6:07 AM (in response to alesj)Thanks Ales for your quick response. I tried adding the exception in the IgnoreSetErrorHandler. It didn't fix the problem :-(.
I read different posts related to this issue. Tried various configurations mentioned in them. But could not resolve the problem. Deleting the jax-rpc, jax-impl jar files solved the class not found exception. But gave another exception.