Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 22591 invoked by uid 500); 19 Mar 2002 09:43:59 -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 22573 invoked from network); 19 Mar 2002 09:43:57 -0000 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: Date: Tue, 19 Mar 2002 09:38:56 +0000 To: Cocoon Dev From: Jeremy Quinn Subject: error handling !*#%! Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Dear All, I am totally mystified as to how you are supposed to handle errors in webapps built using Cocoon. When ever a component in my app throws an exception, I get my (partial) processed XML (as expected) but it is followed by the error definition. That is, I get _two_document_roots_ !!!! How are we supposed to do anything with this? ;) I thought I should be able to insert multiple in individual pipelines to catch that particular problem, this does not appear to work. What I hope to be able to do is this: I have pipelines that assemble via aggregation, from other internal pipelines. If one of those internal pipelines has an error, I get the error XML rather than the content it would have produced ...... this way I can at least respond to the error ...... Is this possible? thanks for any help regards Jeremy -- ___________________________________________________________________ Jeremy Quinn Karma Divers webSpace Design HyperMedia Research Centre --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org