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=5963>.
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=5963

X2-20-Jan: StreamResultAPITest fails only in writeStringToFile() with

           Summary: X2-20-Jan: StreamResultAPITest fails only in
                    writeStringToFile() with
           Product: XalanJ2
           Version: CurrentCVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: org.apache.xalan.serialize
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


TestID: StreamResultAPITest.java testCase2 r1.4
xml-xalan CVS 22-Jan-02 10AM
Three test point 'checkresult's fail in StreamResultAPITest when using 
xercesImpl.jar from Gump on 20-Jan, but only when comparing the files in a 
certain way.
This test performs transformations to in-memory streams of various kinds.  When 
comparing different kinds of streams from the same transformation in memory, 
stream1.toString() and stream2.toString() are equal.  However when writing the 
stream to a file and using writeStringToFile() to compare the data, the actual 
files appear to have additional &#13; characters at the ends of only some of 
the lines in the file.
Xerces 1.4.4 passes this test normally, so this is due to some change in Xerces 
behavior.  Analysis of the test itself will be necessary to see exactly how 
Xerces is getting called.

------- Additional Comments From [EMAIL PROTECTED]  2002-01-22 17:59 -------
Possibly related to bug 5692, except in this case only some lines have the 13's 
on the end.

Reply via email to