Parser2 modification

[Lars Marius Garshol]

 public abstract void setHandler (String handlerID, ModHandler handler)
    throws SAXNotSupportedException;

I think we should allow this method to throw a 
SAXInvalidConfigurationException, to be used to solve the
LexicalHandler/normalize-text problem and similar problems that may
appear with other non-core handlers.

I suggested about 10 seconds ago a SAXInvalidValueException, and I
suppose these two could be merged, since they are roughly the same
thing. 

  public abstract void setFeature (String featureID, boolean state)
    throws SAXNotSupportedException;

Also, I think this method should be allowed to throw the
SAXInvalidConfigurationException so that it can complain about things
like non-existent catalog files, catalog files with syntax errors etc

Or maybe something even more generic would be the best.

--Lars M.


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)