cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: Problems with optional components (servlet, deli)
Date Mon, 14 Jan 2002 15:26:46 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.

I changed the Deli interface now for this. Their is only one method
getting the capabilities for a request object directly.


> 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?
> Cheers
> Carsten
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

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

View raw message