• From: James Clark <jjc@j...>
• To: Xml-Dev List <xml-dev@i...>
• Date: Sun, 19 Apr 1998 14:12:40 +0700

Making the read methods on ByteStream and CharacterStream throw
SAXException seems wrong to me.  In a Java environment I need to be able
to throw an IOException.  So they should be declared as throwing either
Exception or IOException.  The approach in InputStreamAdapter of just
passing through the message from IOExceptions is not acceptable.  An
application may need to deal with different classes of IOExceptions
differently, so it needs to be possible to propagate the IOException up
to Parser.parse.

James


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/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe 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: SAX: 1998-04-18 pre-release
    • From: David Megginson <ak117@f...>
  • Re: SAX: 1998-04-18 pre-release
    • From: Peter Murray-Rust <peter@u...>

• References:
  • SAX: 1998-04-18 pre-release
    • From: David Megginson <ak117@f...>

• Prev by Date: Re: SAX: New Idea for Entity Resolution
• Next by Date: Re: SAX: 1998-04-18 pre-release
• Previous by thread: SAX: 1998-04-18 pre-release
• Next by thread: Re: SAX: 1998-04-18 pre-release
• Index(es):
  • Date
  • Thread