Hopefully you can find something simple to fix this...

Perhaps we can simply make a UCL and set the TCL inside JettyService:

/**
 * The JSP engine (a.k.a Jasper)!
 *
 * The servlet container is responsible for providing a
 * URLClassLoader for the web application context Jasper
 * is being used in. Jasper will try get the Tomcat
 * ServletContext attribute for its ServletContext class
 * loader, if that fails, it uses the parent class loader.
 * In either case, it must be a URLClassLoader.
 *
 * @author Anil K. Vijendran
 * @author Harish Prabandham
 */

Is this spec that it must be a URLClassLoader?

--jason


Adrian Brock wrote:

>No, I'm obviously talking rubbish again.
>
>I think I need to look at how Jetty does the
>classloaders to figure this one out.
>
>At Scott's suggestion, JBossMX remembers the
>context classloader from the MBean's registration and
>uses it again during MBean invocation. It has to be
>something to do with that.
>
>Regards,
>Adrian
>
>>I can't speak for apache/jasper.
>>
>>But (I think) with JBossMX jasper gets the apps
>>UnifiedClassLoader instead of JettyService's
>>MBeanClassLoader.
>>
>>The "I think" is because I haven't actually verified
>>this.
>>I do know the WebIntegration tests don't have the JSP
>>problems running under JBossMX that it does with the
>>RI.
>>
>>Regards,
>>Adrian
>>
>>>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-dev
>>
>>>lopment
>>>
>
>
>
>_________________________________________________________
>View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=10040
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jboss-development
>



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

Reply via email to