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=5968>. 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=5968 X2-20-Jan:SystemIdImpInclTest has excess one test point Summary: X2-20-Jan:SystemIdImpInclTest has excess one test point Product: XalanJ2 Version: CurrentCVS Platform: All OS/Version: All Status: NEW Severity: Normal Priority: High Component: org.apache.xalan.serialize AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] TestID: SystemIdImpInclTest.java testCase1 r1.8 xml-xalan CVS 22-Jan-02 10AM; xercesImpl.jar from Gump on 20-Jan One test point fails in testCase1 when using this version of Xerces because every output line has an additional at the end. Actual incorrect output: <?xml version="1.0" encoding="UTF-8"?> <out> <include-list-level2><import-list-level2> <matched-by-main>Above Should be include-list then import-list</matched-by- main> <matched-by-main>This is SystemIdImpIncl.xml, used for setSystemId testing Note that different settings of systemIds will have different expected results! </matched-by-main> <matched-by-import-level2>Should be matched-by-import</matched-by-import- level2> <matched-by-include-level2>Should be matched-by-include</matched-by-include- level2> <matched-by-import-also-level2>Should be matched-by-import-also</matched-by- import-also-level2> <include-list-level2><import-list-level2> <matched-by-main>Should be matched-by-main</matched-by-main> <matched-by-main>Should be matched-by-main</matched-by-main> </import-list-level2></include-list-level2> </import-list-level2></include-list-level2> </out> Note that this may be related to bug 5962 and 5963, although this one should be easiest to diagnose since it repeats a very similar algorithim several times, and only one specific checkresult fails: "transform after setSystemId(xslonly level2) into results- api\SystemIdImpInclTest\trax\SystemIdImpInclTest_4.out" The only apparent difference between this failing checkresult and the immediately preceeding one is that when the StreamSource(FileInputStream (xmlName)) object is created, in the passing case it has the correct systemId set, and in the failing case it does *not* have any systemId set. This should not affect the test, since the StreamSource(FileInputStream(xslName)) does have a legal systemId set in both cases which it uses to resolve xsl:include, etc. ------- Additional Comments From [EMAIL PROTECTED] 2002-01-22 20:26 ------- See also bug 5962 and bug 5963.
