Saxon

Legacy ID: #4672621 Legacy Poster: Chapman Flack (jcflack)

Hi, I just upgraded to Saxon-B 9.0.0.2J and straightaway an application blew up that synthesizes a document via a SAXSource with a custom XMLReader. net.sf.saxon.event.Sender (around line 336) throws exceptions if it is handed an XMLReader that does not recognize or does not support the http://xml.org/sax/properties/lexical-handler property. But according to both http://sax.sourceforge.net/apidoc/org/xml/sax/package-summary.html#package_description and http://java.sun.com/javase/6/docs/api/org/xml/sax/XMLReader.html#setProperty(java.lang.String,%20java.lang.Object) all such properties are optional; an XMLReader need not recognize or support any at all. I can work around the problem by adding the logic below to every custom XMLReader given to Saxon. But that should not be necessary, and technically makes the XMLReader less strictly compliant (as, if it does nothing with the lh property, it really should report that by throwing the specified exception). Chapman Flack private static final String propertyLexicalHandler //add = "http://xml.org/sax/properties/lexical-handler"; //add Object lh; //add public Object getProperty( String name) throws SAXNotRecognizedException, SAXNotSupportedException { if ( propertyLexicalHandler == name ) //add return lh; //add else //add throw new SAXNotRecognizedException( name); } public void setProperty( String name, Object value) throws SAXNotRecognizedException, SAXNotSupportedException { if ( propertyLexicalHandler == name ) //add lh = value; //add else //add throw new SAXNotRecognizedException( name); }