Cart
[Home] [By Thread] [By Date] [Recent Entries]
I've just switched XP to use the exception handling approach I'm advocating for SAX, and I'm very happy with it: - if you import com.jclark.xml.parse.*; import com.jclark.xml.parse.io.*; you get an interface where the handler methods can throw IOException and where the parse method throws IOException (the same as the old XP interface) - if you import com.jclark.xml.parse.*; import com.jclark.xml.parse.awt.*; you get an interface where the handler methods can throw AWTException and where the parse method throws AWTException and IOException; - if your application needs to throw some other kind of exception, you can either create a package with 4 trivial wrapper classes (which could be automatically generated from the com.jclark.xml.parse.awt.* source), or you can use com.jclark.xml.parse.base.* where the handler methods are declared as throwing Exception and the parse method is declared as throwing IOException and ApplicationException (which is a wrapper analagous to SAXException). 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...)
|
