cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: JNDI in cocoon (related to ClassLoader issues)
Date Sat, 15 Jun 2002 15:22:35 GMT
Sylvain Wallez wrote:

> This is now fixed, but this problem is very likely to resurface with
> Cocoon blocks : if a block comes with its own jars, Cocoon will have to
> create a classloader for them and set it as the context classloader so
> that block-defined classes can be loaded correctly by Avalon.

Yes, this assumption is absolutely correct. Each block will require its
own classloader, there is no way to escape this.

> Tomcat seems to be ok now by travelling up the classloader hierarchy,
> but what about other servlet containers ?

Gosh, I don't know that.

Do we have any information on that?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message