SAX RFD: ModSAX Predefined Features

[David Megginson]

John Cowan writes:
 > David Megginson wrote:
 > 
 > >   public abstract void setFeature (String featureID, boolean state)
 > >     throws SAXNotSupportedException;
 > 
 > I want to propose a restriction and an extension:
 > 
 > 1) This method cannot be called after any other parser method
 > has been invoked.

Wouldn't it be better to allow the parser/filter make that decision?
If the user attempts to change something during a parse that should
*not* be changed during a parse, the parser/filter can throw a
SAXNotSupportedException.

 > 2) This method is allowed to throw a SAXNewParserException, which
 > encapsulates a replacement parser.  The application should use
 > the parser inside the exception in place of the original parser.
 > This allows parsers to push filters on top of themselves, which
 > complements the ability of applications to push them.

I think that this could be layered on top of SAX, simply by
subclassing SAXNotSupportedException.


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)