Saxon

It's treating the FODC0002 error as a warning because Controller.getRecoveryPolicy() is set to RECOVER_WITH_WARNINGS.

This behaviour for the document() function is still permitted in XSLT 3.0: If an error occurs during evaluation of the docFO30 function, the processor may either signal this error in the normal way, or may recover by ignoring the failure, in which case the failing URI will not contribute any nodes to the result of the document function.

The test metadata, however, specifies <ignore_doc_failure satisfied="false"/>

This is causing the recovery policy to be set to DO_NOT_RECOVER on the CompilerInfo. However, the recoveryPolicy on the PreparedStylesheet isn't set from this value.

The s9api XsltCompiler wraps a CompilerInfo with the correct recoverPolicy = 2. We call loadExecutablePackage() on this XsltCompiler to create an XsltPackage which knows nothing of the recovery policy. Then we call link() on the XsltPackage, which creates the PreparedStylesheet and wraps it in an XsltExecutable.

The link() method in fact creates a new CompilerInfo, using the default compilation properties on the Configuration, rather than those used to compile the package.

Changing the XsltPackage to retain a reference to the XsltCompiler, and using this to get the original CompilerInfo, solves the problem.