I'd be willing to help with this issue, but from my point of view there are
two possibilities :
1. We revert the JasperLoader changes back to parent.loadClass(name) call.
2. We modify Catalina to set the contextClassLoader during an include or a
forward call.
I still wonder which is the best approach, but I must say I don't quite
understand why we have to store the class loader in the Thread. It seems a
tad ugly to do it that way...
Best greetings,
Serge...
At 13:53 07.08.2001 -0700, you wrote:
>Quoting Serge Huber <[EMAIL PROTECTED]>:
>
> > Hi all,
> >
> > I am using a RequestDispatcher to do a cross context include to a JSP.
> > The
> > problem is there seems to be a problem in the JasperLoader
> > implementation.
> > Let me explain quickly the configuration :
> >
> > contextA :
> > - does a
> >
> getContext("/contextB").getRequestDispatcher("path/file.jsp").include(request,
> >
> > response) call
>
>I just checked and cross-context includes and forwards have a problem.
>You can use a redirect as a workaround with b6.
>
>Remy
