Hello Scott,
I noticed this behaviour in the parser awhile ago. For each SAX parser
instance, there exists only one XMLAttributes instance which is reused for
every new set of attributes. So, on each startElement() call, the previous
values in this object will have been overwritten.
SAX doesn't s
During the startElement() method in a ContentHandler implementation, I store a
reference to the Attributes parameter and later attempt to use it in
endElement(). What I experience in endElement(), however, is that the
variable no longer contains the same data. It now contains data of another
Hi, I
am using Xalan 1.4 C++ and Java. Whenever any error occurs in
thetransformation, Xalan prints the error on console (std err). I donot want
iton console. How to suppress
it?CheersKumaravel
The feature you mentioned is set to false and I still get the exception.
The stack trace is:
org.xml.sax.SAXNotRecognizedException:
http://apache.org/xml/properties/dom/current-element-node
at
org.apache.xerces.parsers.DOMParser.getProperty(DOMParser.java:496)
at
com.ibm.amit.parser.DO
