Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 51838 invoked by uid 500); 12 Jul 2001 16:33:51 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 51518 invoked from network); 12 Jul 2001 16:33:26 -0000 Date: Thu, 12 Jul 2001 12:33:18 -0400 (EDT) From: Donald Ball X-X-Sender: To: Subject: Re: AW: [C2] handle-errors with content aggregation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N 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: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org