Saxon

I've created a JUnit test case: TestXsltCompiler/testErrorNotificationFromImportSchemaError

This is showing up another related problem: the URIResolver registered with the XsltCompiler is not being used to resolve the schema-location appearing in xsl:import-schema. I'm not sure there's any specification that says it should be so used, but it seems a reasonable expectation.

Note that this doesn't apply to JAXP, where it's not possible to specify an ErrorListener or URIResolver at the level of an individual stylesheet compilation, they can only be specified at global (factory) level.

Not sure why this was dropped.

It seems a series of new JUnit tests were added to TestXsltCompiler on the 9.9 branch, some of which aren't passing. The tests weren't copied over to the 10.0 branch; I've now done that, and the same situation applies.

The test testErrorNotificationFromImportSchemaError, although it passes, is not achieving the desired effect. Rather, it reveals that the URIResolver registered with the XsltCompiler is not being used to resolve the schemaLocation appearing in the xsl:import-schema declaration. The Javadoc for XsltCompiler.setURIResolver() says clearly that it should be used, so I will change this.

With this fixed, the actual error in the schema (an invalid QName) is notified to the StandardErrorReporter, and the final "schema compilation has failed" is reported to the XsltCompiler's errorListener. This is still wrong; both should go to the XsltCompiler's errorListener. That requires a simple change to the way XslImportSchema sets up its PipelineConfiguration. This works. And it still works when I change the test to use XsltCompiler.setErrorList() to capture the errors.

With some corrections to the test, testErrorNotificationFromInlineSchemaError also now passes.