[
Lists Home |
Date Index |
Thread Index
]
- From: "Don Park" <donpark@quake.net>
- To: "David Megginson" <ak117@freenet.carleton.ca>, "xml-dev Mailing List" <xml-dev@ic.ac.uk>
- 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@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|