OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Re: [Sax-devel] Re: [xml-dev] SAX/Java ProposedChanges

[ Lists Home | Date Index | Thread Index ]

At 12:47 PM -0500 3/5/04, Karl Waclawek wrote:

>The question is: why can the exception argument passed to fataError()
>wrap another exeption then?

Because it's sometimes useful to do so. For instance, the parser 
might detect a well-formedness error when Reader.read throws a 
CharacterConversionException. It could then stick this exception into 
the exception field of the SAXException, so it could be further 
inspected, in a debugger for example. The goal here is to provide 
additional information about the cause of one exceptional condition, 
not to chain together a bunch of exceptions that each represent a 
different error in the same document.

In Java 1.4 all exceptions, in fact all throwables, can have nested 
exceptions. This is a general pattern that makes debugging easier. It 
is not meant stuff several exceptional conditions into one object. 
Instead it is meant to provide different views of a single 
exceptional condition.


   Elliotte Rusty Harold
   Effective XML (Addison-Wesley, 2003)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS