cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers" <Ralph.Go...@dslextreme.com>
Subject Re: question about jar conflicts/java class loading conflicts
Date Thu, 18 Nov 2004 17:33:06 GMT
Sylvain Wallez said:
> Eric Bloch wrote:
>
>>
> Actually, it writing your own classloader *does* solve the problem.
> Cocoon provided a so-called "paranoid" block providing a
> "ParanoidCocoonServlet". This servlet loads the Cocoon servlet (or any
> other servlet through a config in web.xml) in a ParanoidClassLoader that
> shields the webapp's classes from the upper-level classloaders.
>
> Shielding means that classes and resources are always looked up _first_
> in the webapp before delegating to the parent classloader. Up to now,
> this has always saved my life in crazy classloading environments ;-)

I don't believe this will save you in some environments.  I've been told
that JBoss appears to have problems with the logging classes. I've been
told that it expects to get them from its class loader and if it gets them
from the webapp it seems to fall apart.

Ralph


Mime
View raw message