Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>:

> See below.
> 
> On Thu, 31 May 2001, Remy Maucherat wrote:
> 
> 
> I'm not sure this proposed change would really make any difference. 
> The
> "parent" classloader here is the web app classloader already, which is
> the
> same thing that the context class loader is set to.
> 
> NOTE:  If we do something like this, we need to make sure that
> getResource() and getResourceAsStream() work in JasperLoader as well.
> 
> I'll do some more investigation today.

Apparently, the problem was that the parent reference wasn't reset after 
reloading. So using a dynamic call would solve this.

Remy

Reply via email to