Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 76032 invoked by uid 500); 1 Jul 2003 15:46:53 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 76016 invoked from network); 1 Jul 2003 15:46:52 -0000 Received: from mailhost.softeam.fr (194.2.241.2) by daedalus.apache.org with SMTP; 1 Jul 2003 15:46:52 -0000 Received: from rw2kwoopseval ([194.214.220.147]) by mailhost.softeam.fr (8.9.3/93idpgr-1.2.13) with SMTP id RAA27851 for ; Tue, 1 Jul 2003 17:46:23 +0200 (MET DST) Message-ID: <01cd01c33fe8$30c0a540$93dcd6c2@rw2kwoopseval> From: "Eddy Fras" To: Subject: Pipelines and error handling Date: Tue, 1 Jul 2003 17:44:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I have a problem with Cocoon 2.0.4 and error handling in a homemade Transformer. I declared an error-handler in my sitemap and when a SAX exception is thrown in the transformer, the handler applies a specific XSL stylesheet on the generated error code. The problem is that when the error occurs, the transformer may have begun to send SAX events into the pipeline to the next component. If this is not the case, everything is fine. If this is the case, the error message is displayed but the browser does not close the connection and is still waiting for something. Do I have to explicitely stop the current pipeline before starting the error pipeline ? Thanks for your help, Eddy --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org