• From: "Don Park" <donpark@q...>
• To: "David Megginson" <ak117@f...>, "xml-dev Mailing List" <xml-dev@i...>
• Date: Wed, 7 Jan 1998 20:28:28 -0800

David,

>Does it make sense, then, simply to allow every method in the SAX/Java
>interfaces to throw java.lang.Exception?
>
>  package org.xml.sax.DocumentHandler {
>    public void startDocument () throws java.lang.Exception;
>    public void endDocument () throws java.lang.Exception;
>    /* etc. */
>  }


Allowing every method in SAX interfaces to throw java.lang.Exception
basically disables Java compile-time exception checking.  I do not think
this is a good idea.

How about defining ApplicationException class which is basicaly an exception
container?

public void startDocument () throws ApplicationException {
    try {
        // some IO
    }
    catch (Exception ex) {
        throw new ApplicationException(ex);
    }
}

Don Park



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

• Prev by Date: SAX: Exceptions in Java SAX Implementation
• Next by Date: Re: SAX: Naming and Packaging (question 10 of 10)
• Previous by thread: SAX: Exceptions in Java SAX Implementation
• Next by thread: LISTRIVIA: multiple postings
• Index(es):
  • Date
  • Thread