Hi, mabye anybody around here has come across this situation.
Recently the ASF Gump instance has started to make sure XMLUnit's unit tests run on Xerces and Xalan rather than the parser/transformer of the JDK. This is when the tests started to fail, the only remaining failure can be seen here: http://vmgump.apache.org/gump/public/xmlunit/xmlunit-test/gump_file/TEST-org.custommonkey.xmlunit.test_Transform.xml.html The test uses a stylesheet containing an xsl:include that cannot be resolved and expects the transformer to throw an exception. In Xalan's case this does not happen. As can be seen in the log the error and not the fatalError message of the attached ErrorListener is invoked so it seems Xalan doesn't consider the failing include fatal. The JAXP docs on URI resolver aren't really clear on what is to be expected if the resolution fails (or maybe I'm just not finding the right doc). Does anybody know whether it is OK for Xalan to treat the failing include as non-fatal or whether I should report a bug? Stefan ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Xmlunit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmlunit-general
