Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Mon, 8 Mar 1999 14:50:25 -0500 (EST)
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
> 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
All the best,
David Megginson email@example.com
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)