cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: Moved ParanoidCocoonServlet to its own block
Date Fri, 12 Dec 2003 01:03:06 GMT

On 11 Dec 2003, at 13:53, Sylvain Wallez wrote:

> Last one for today ;-)
> I moved the ParanoidCocoonServlet and associated classes to a new 
> "paranoid" block?
> Why this? Because ParanoidCocoonServlet is actually a generic servlet 
> wrapper that can shield _any_ servlet in a ParanoidClassLoader. Moving 
> it to its own block leads to having a "cocoon-paranoid-block.jar" that 
> can be deployed separately from "cocoon.jar".
> This allows several things:
> - use the ParanoidCocoonServlet with another servlet. Yes, remember 
> Cocoon isn't the only servlet ;-)
> - leave only paranoid.jar in WEB-INF/lib and have all other libs 
> located somewhere else by using the "paranoid-classpath" init 
> parameter.
> I use this second feature to load "build/eclipse/classes" in Jetty. 
> This allows faster roundtrips since it removes the need to "build 
> webapp" at each code change.

Uh, can you elaborate more on this? I'm very interested in knowing how 
you develop on eclipse.


View raw message