B
badgerduke
I had an operable SAX parser running on WebSphere 4.0 which I
transferred to run on Tomcat 5.x. This broke the parser. It still
validates against a schema ( I am using Xerces with an XMLReader).
Among the strange behavior . . . characters() methods sometimes take in
a char array of length 2048 (2k). The whitespace after the end of each
element is not ignored (it fires characters()). It is not before too
long that a NumberFormatException occurs and my parser stops cold.
I am not allowed to show code here, but I hope somebody relates to this
erratic behavior. I have considered a conflict but haven't found it if
it exists.
transferred to run on Tomcat 5.x. This broke the parser. It still
validates against a schema ( I am using Xerces with an XMLReader).
Among the strange behavior . . . characters() methods sometimes take in
a char array of length 2048 (2k). The whitespace after the end of each
element is not ignored (it fires characters()). It is not before too
long that a NumberFormatException occurs and my parser stops cold.
I am not allowed to show code here, but I hope somebody relates to this
erratic behavior. I have considered a conflict but haven't found it if
it exists.