On Thu, 12 Jul 2001, Carsten Ziegeler wrote:
> With the current design of cocoon2 it is not possible to have always a
> clean error page.
> The problem is that the components, e.g. the content aggregation write
> directly to the output stream. If some components have written something
> and an error occurs it is forbidden by the servlet engine to do a redirect
> and the output stream cannot be reset.
>
> I wanted to address this problem by the concept of an intermediate output
> stream, but there is currently no consense found.
consensus seemed to be that an intermediate output stream was fine as long
as we could configure it on or off on a per-sitemap or per-pipeline basis.
that was my impression anyway. does anyone disagree with this?
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
