[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX2: Should SAXException extend IOException?

• From: Rajiv Mordani <Rajiv.Mordani@e...>
• To: David Megginson <david@m...>
• Date: Wed, 22 Dec 1999 11:34:53 -0800 (PST)

java.util.zip.ZipException deriving from IOException is appropriate. It is
related to i/o so it makes sense to have that. Incase of
java.net.MalformedURLExcetion ther could be an argument why it derives
from IOException. However in case of SAX it is a callback mechanism It
doesn't do the IO operations. It is the parser code / the person
implementing the xml file handling doing that. So if any IO errors occur
it will be detected earlier on, before the callback happens. Hence I don't
see the rationale in making the SAXHandlers throw IOException. It is just
a callbck/event mechanism which occurs after IO operations have been done
it should derive from RuntimeException rather than IOException IMHO. 

- Rajiv

On Wed, 22 Dec 1999, David Megginson wrote:

> Rajiv Mordani writes:
> 
>  > I am not sure what the intent is of having IOException. I think
>  > SAXException seems appropriate to me..
> 
> I'd like to hear as many opinions on this point as possible.  What is
> the rationale for *not* deriving SAXException from IOException when
> (for example) java.net.MalformedURLException and
> java.util.zip.ZipException are derived from IOException?
> 
> I especially like the idea that higher-level libraries could have
> 
>   void importXML (String uri) throws IOException;
> 
> without the application's having any direct dependency on SAX
> interfaces.  It could accomplish the same thing by having a
> SAXExceptionAdapter that embeds the SAXException and extends
> IOException, but that seems like a lot of unnecessary fuss for a very
> common case.
> 
> Opinions?
> 
> 
> All the best,
> 
> 
> David
> 
> -- 
> David Megginson                 david@m...
>            http://www.megginson.com/
> 
> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
> To unsubscribe, mailto:majordomo@i... the following message;
> unsubscribe xml-dev
> To subscribe to the digests, mailto:majordomo@i... the following message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa@i...)
> 
> 


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: SAX2: Should SAXException extend IOException?
    • From: David Megginson <david@m...>

• References:
  • SAX2: Should SAXException extend IOException?
    • From: David Megginson <david@m...>

• Prev by Date: RE: Survey: Catalysis Templates
• Next by Date: Re: XML Indexing Engine
• Previous by thread: SAX2: Should SAXException extend IOException?
• Next by thread: Re: SAX2: Should SAXException extend IOException?
• Index(es):
  • Date
  • Thread