[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: SAX2: Parser interface
> public void setProperty (String property, Object value) > throws SAXNotRecognizedException, SAXNotSupportedException; > public Object getProperty (String property) > throws SAXNotRecognizedException; <snip!> > 2. Extended handler types (for schemas, or what-have-you) can be set > using the setProperty method with the appropriate URI identifier. <snip!> > 3. Should we just use setProperty to set the optional handlers? Couldn't there be a SAX2 Handler interface public interface Handler { } which marks a SAX2 Handler. The other handler interfaces are subclasses of this. Giving a generic: public void setHandler(Handler handler, String identifier) throws SAXNotRecognizedException, SAXNotSupportedException; - identifiers for the standard handlers can be provided (e.g. as public final constants) - additional extended handlers use the same method to register, only using the appropriate URI identifier as you suggest. IMHO this is a cleaner way of registering handlers. I don't have to remember that one Handler is registered explicitly (setDTDHandler) and another through a setProperty call. A Handler isNotA property. Cheers, L. 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...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|