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=4606>. 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=4606 xerces2b3: DOMSource with no systemId no longer throws exception Summary: xerces2b3: DOMSource with no systemId no longer throws exception Product: XalanJ2 Version: CurrentCVS Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: org.apache.xalan AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] TestId:SAXTransformerFactoryAPITest.java r1.7 SAXTFactoryTest004 With xml-xalan from CVS 02-Nov-01 and simply switching java/bin/xerces.jar to the 2.0beta3 jar, this test changes behavior. This test case builds a DOMSource from a Node from parsing citiesinclude.xsl, explicitly without setting the systemId. The stylesheet merely has one line: <xsl:include href="../cities.xsl"/> When we attempt to use this DOMSource to perform a transformation using SAX, we expect (and xerces1 does this) it to throw an exception since it cannot find the included file. However xerces2 simply lets processing complete; the transformation even produces an output file with just the xml decl in it, nothing else.
