Does anyone know why the Jasper JspSevlet thinks that its TCL is always 
a URLClassLoader?  It takes the value from 
Thread.currentThread().getContextClassLoader() and casts it with out a 
care... does the same for getClass().getClassLoader()...

It is assigning the value parentClassLoader, which is of type 
URLClassLoader... but then they have checks for if (parentClassLoader 
instanceof URLClassLoader).

This is garbage...

Anyways, I am seeing consistent ClassCastExceptions for 
MBeanClassLoader... which is not a URLClassLoader.  My guess is that 
MBeanClassLoader could be a URLClassLoader, but that seems a bit artificial.

Anybody know what is up with this?

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to