cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: Problems with optional components (servlet, deli)
Date Tue, 15 Jan 2002 14:07:41 GMT
Carsten Ziegeler wrote:

> Hi,
> I'm just in the process of making as much as possible of the compilation
> optional in Cocoon.
> There are some problems, here are two of them:
> The deli package can not be left out as the components.deli.Deli interface
> directly imports hp classes. As this interface is required by the
> traxtransformer,
> the hp classes are required even if the DeliImpl is left out.

Try running Cocoon without Deli (be sure to remove the definition from the
Cocoon.roles file).  It should work (I tested it before I committed my

> The second problem is the independence of the servlet api. We pray that
> cocoon is independent but for compiling (and running) cocoon the servlet
> classes are required even for cli. After patching some parts, there is
> only one place left: the abstract sitemap class. It contains the
> tryToResetResponse
> method which explicitly tests against an HttpResponse class, which is
> very bad! For separation concerns I would like to add a tryToResetResponse
> on the environment interface. Anything against this?

+1.  Nothing outside of the CocoonServlet API should directly use the Servlet


"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin

To unsubscribe, e-mail:
For additional commands, email:

View raw message