We've overrode startElement(), endElement(), and characters().
In our characters() method, the current code (a lot of it) considers the invocation of characters() to mean that all of the element's value (the "Hello" in <world>Hello</world) is complete and then goes thru a large if/else-if/else-if/... try/catch(es) statement. Then the endElement() is invoked and more if/else-if/... try/catch(es) statements are executed.
I've read that the semantics of characters() is that it is invoked multiple times if the element's value contains multiple lines and really characters() method should just "buffer" its value. And only once endElement() is called then and only then is the element's value is complete.
Because there is a lot of code, my question is if the default functionality can be overridden in the SAX parser so that characters() is called once irrelevant if the element's value contains multiple lines or not?
We're not running Java (on Windows/Unix) with any special options other than "java -cp . MyParser my_data.xml"
Author and all-around good cowpoke
posted 6 years ago
The behavior of characters() is rock hard encoded into the SAX api.
You could use the StaX parser approach. See javax.xml.stream package.
As I understand it, when the StaX parser hands you a Characters event all of the element text is available in that event.
If you wrote a lot of code assuming behavior of characters() that does not correspond to the API, regard it as a learning experience.