> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sylvain Wallez > Sent: Thursday, December 11, 2003 10:54 PM > To: [EMAIL PROTECTED] > Subject: Moved ParanoidCocoonServlet to its own block > > > 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.
Cool thing. One question: If I don't package Cocoon and use the compiled classes directly Flowscript doesn't work any more (It's a problem with the FOM_Cocoon object because if I delete it and use the classes from the package Flowscript works again) . Anybody out there with the same/similar problem(s)? -- Reinhard
