You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/06/26 03:53:13 UTC

DO NOT REPLY [Bug 7368] - Text Nodes are split randomly

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 mcoarr@mitre.org  2002-06-26 01:53 -------
We are encountering what we believe to be a similar problem, though our
circumstances are a little different.

Our particular problem manifests (on infrequent occasions) itself during a null
(aka identity) transform.  It seems that what might be happening is that two
text nodes are created for the text value of an element and their order is
transposed.

For instance, we start out with something like
<arrival_date_time>2002-06-25T21:45:00</arrival_date_time> but we end up with
<arrival_date_time>:45:002002-06-25T21</arrival_date_time> after the null
transform, or something similar.  

FYI, we probably get errors on the order of one in 300 elements processed (only
looking at these date elements).

Here's the basic idea of what we are doing (using jaxp interfaces):
1. open input stream from http request.
2. create StreamSource object
3. get null/identity transformer from factory
4. create StreamResult object
5. perform transform