DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7368>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7368 Text Nodes are split randomly ------- Additional Comments From [EMAIL PROTECTED] 2002-03-22 19:53 ------- Hmm... We are not using SAX at all in the processing. Immediately after the transformation, you can view the contents of the extractRootNode variable in a debugger (in this case, JSwat). Then, already, you can see that the structure of the DOM tree is wrong: in the tree, an element "id" has firstChild, of type TextImpl, with data 0037. This TextImpl, in turn, has nextSibling, again of type TextImpl, with data 09320238. However, the XML contains: <id>003709320238</id> So it doesn't seem to me that incorrect SAX usage would be the problem. Unfortunately, the files in question are our clients' invoice files, and I can't pass them on to you, at least not until I get a permission from the senders. The behavior does occur a lot in our system, though: in just a week, we received more than 10 of these problematic files in our live installation, which we then processed by manually splitting the file into two or more parts; then they went through (though the processing logic stayed the same). It is this slight nondeterminism that makes me think there may be a bug in Xalan, rather than in our code...
