[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Catching Parser/Transformer Exceptions Xerces and Saxon

---

---

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().

But it may be better to set up an ErrorHandler associated with the XML
parser, so you are informed of XML parsing errors directly.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] 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

---