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 seems wrong, as blocks are to be hot-deployed by Cocoon, and this is instead an integral part of Cocoon that must be in the classpath before Cocoon starts.
For this, it was initially thought to use "modules", ie exactly the same thing that is now done with blocks, but that would not change later into real blocks.
Is it ok if I move it to a "modules" section and add the build of modules as for blocks?
I understand your concern. But what other "blocks" would be candidates for "modules"? Can we foresee that Cocoon's core and the various environments can be modules too?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
