Re: [basex-talk] Issue with the Java 11 XML Catalog API and xsl:import/xsl:include

Hi Gerrit, In the latest snapshot [1], the unexpected exception was replaced by controlled error feedback. I assume we cannot fix the underlying problem, as the error is raised by Java’s catalog resolver. It’s certainly a good idea to resort to Norm’s up-to-date XML resolver. Cheers, Christian

Re: [basex-talk] Issue with the Java 11 XML Catalog API and xsl:import/xsl:include

Hi Gerrit, Thanks for the report. I’m pretty sure we can (and should) return a proper error message. It may be trickier to find out why the paths are not resolved by the new Catalog API. I’ve opened an issue on that [1], and I’m glad to hear that Norm’s XML resolver can cope with your input. All

Re: [basex-talk] Issue with the Java 11 XML Catalog API and xsl:import/xsl:include

(I forgot to mention that saxon-pe-10.6.jar is also in lib/custom) On 08.03.2023 13:08, Imsieke, Gerrit, le-tex wrote: Hi, We experience an issue with the new catalog resolver when importing or including XSLT from another, possibly already catalog-resolved, XSLT file. If you unzip attached

[basex-talk] Issue with the Java 11 XML Catalog API and xsl:import/xsl:include

Hi, We experience an issue with the new catalog resolver when importing or including XSLT from another, possibly already catalog-resolved, XSLT file. If you unzip attached catalog_test.zip and set the catalog location by a pragma around xsl.xq or by set