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
Ok thanks a lot.
Yes I did miss the commit message (I have them filtered to another folder)
! Thanks a lot for the quick fix !
Best greetings,
Serge Huber...
At 09:25 08.08.2001 -0700, you wrote:
2 is the only correct one, since if you forward to a servlet, it wouldn't
work
contextA to contextB. So
that when JasperLoader executes in contextB, it actually tries to load
classes using the class loader of contextA.
Did I miss something in configuration or is this a bug ?
Best greetings,
Serge Huber.
[EMAIL PROTECTED]
and
that I am willing to patch tomcat code if needed.
Thanks a lot,
Serge Huber.
. Any proposed patch would
*definitely* be welcome.
Craig
On Fri, 27 Apr 2001, Serge Huber wrote:
Hi all,
I am using cross context dispatching in one of my web applications. In
order to do this I have the following setup in my server.xml file :
DefaultContext crossContext
error.
greetings,
Serge...
At 20:52 26.04.2001 -0700, you wrote:
Yep, that definitely looks like a bug. Any proposed patch would
*definitely* be welcome.
Craig
On Fri, 27 Apr 2001, Serge Huber wrote:
Hi all,
I am using cross context dispatching in one of my web applications
