This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Catching Parser/Transformer Exceptions Xerces and Saxon
- From: "Mark R. Diggory" <mdiggory at latte dot harvard dot edu>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 08 Aug 2002 10:14:49 -0400
- Subject: Re: [xsl] Catching Parser/Transformer Exceptions Xerces and Saxon
- References: <000101c23e61$97c0cce0$6401a8c0@pcukmka>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Michael Kay wrote:
If there's a parsing error, then the TransformerException thrown by
Saxon will encapsulate the SAXException thrown by the XML parser - you
can get it by calling getException().
Hmmm, This may be a bug then, because I am not getting the encapsulated
SAX Exception. I am working with tomcat 4.0.3's default Xerces version.
I think it is
* xerces.jar - The Xerces 1.x XML parser (also includes the JAXP 1.1
interfaces).
probibly version 1.4 but I will doublecheck this shortly.
But it may be better to set up an ErrorHandler associated with the XML
parser, so you are informed of XML parsing errors directly.
Yes, I think I will try this in my code.
thanks,
Mark Diggory
Michael Kay
Software AG
home: Michael.H.Kay@ntlworld.com
work: Michael.Kay@softwareag.com
-----Original Message-----
From: owner-xsl-list@lists.mulberrytech.com
[mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of
Mark R. Diggory
Sent: 07 August 2002 22:08
To: xsl-list
Subject: [xsl] Catching Parser/Transformer Exceptions Xerces and Saxon
Hi All,
I've been playing around with putting Xerces infront of Saxon
and trying
use it's validating features to validate the xml prior to transform.
However, the javax.xml.transform.TransformerException coming out of
Saxon doesn't seem to retain any information about the
parsing exception
that occured in Xerces. Is there a feature or something in Saxon or
Xerces that I am missing? I'm using the JAXP interfaces and
I'm setting
up an XMLReader as the source for the XML being transformed by
Transformer. I'd like to be able to tell if the document was
invalid vs.
other problems that could occur in the parser.
-Mark Diggory
Harvard MIT Data Center
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list