Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 49619 invoked from network); 24 Nov 2003 11:18:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Nov 2003 11:18:50 -0000 Received: (qmail 20284 invoked by uid 500); 24 Nov 2003 11:18:14 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 20263 invoked by uid 500); 24 Nov 2003 11:18:14 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 20250 invoked from network); 24 Nov 2003 11:18:13 -0000 Received: from unknown (HELO mx.4dconcept.fr) (195.134.212.162) by daedalus.apache.org with SMTP; 24 Nov 2003 11:18:13 -0000 Received: from pc-016.4dconcept.fr (mx.4dconcept.fr [195.134.212.162]) by mx.4dconcept.fr (Postfix) with ESMTP id 1475217815 for ; Mon, 24 Nov 2003 12:15:20 +0100 (CET) Message-Id: <5.2.0.9.2.20031124121151.00b17fa8@10.0.0.162> X-Sender: lcrine@10.0.0.162 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 24 Nov 2003 12:18:25 +0100 To: users@cocoon.apache.org From: Lionel Crine Subject: Re: Handling SAX Exceptions in sitemap In-Reply-To: <3FC1E63E.9090201@misgl.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N hi, If you're using the common xslt transformer, you should look at the source. If the methods don't throw any exception, so you can't catch the exception= =20 with the handle-errors. If you're using Cocoon 2.1, you can customize the exception.Search the= archive. Lionel At 11:06 24/11/2003 +0000, you wrote: >Hi, > >Does anyone know if it is possible to handle SAX exceptions thrown by a=20 >transformer using a error handler defined in a sitemap. > >Here is a brief test to explain what I am trying to achieve. > > > > src=3D"fragments/test.xml"/> src=3D"xsl/testtrans.xsl"/> type=3D"xml"/> > > > > > > > > >If I rename the file "test.xml" to force a filenotfound exception in the=20 >generator then the pipeline level error handler is correctly invoked. > >However if the generator stage succeeds but then a SAX exception occurs >in the transformer my error handler is not invoked and an >"XML Parsing Error: no element found " >is sent to my browser. > > >It may be that I am approaching this in the wrong way but is there >any way of defining an error handler that will be invoked despite >where in the pipeline the error occurs. ie can transform errors be caught= =20 >in the sitemap. > >Any help would be much appreciated. > >Thanks > >Si > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org >For additional commands, e-mail: users-help@cocoon.apache.org Lionel CRINE Ing=E9nieur Syst=E8mes documentaires Soci=E9t=E9 : 4DConcept 22 rue Etienne de Jouy 78353 JOUY EN JOSAS Tel : 01.34.58.70.70 Fax : 01.39.58.70.70 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org