Guys,
I followed the discussion, and I want to add two things about handle-errors
and content aggregation, both causing a somewhat surprising behaviour of
cocoon when an error occurs:
1. I wondered why the handle-errors finishes the content aggregation when an
error occurs. When I aggregate 4 par
> > > 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
