Hi Christian, Thank you for your reply! That makes sense. I worked around the problem for now by implementing an XML Catalog Resolver in XQuery. I've made it available on GitHub in case other people might need it.
For example: import module namespace resolver = "xml-catalog-resolver" at "https://raw.githubusercontent.com/vincentml/xml-catalog-resolver/main/xml-catalog-resolver.xqm";; let $doc := "example.xml" let $catfile := db:option("catfile") return resolver:parse-xml($doc, $catfile) Kind regards, Vincent _____________________________________________ Vincent M. Lizzi Head of Information Standards | Taylor & Francis Group vincent.li...@taylorandfrancis.com Information Classification: General -----Original Message----- From: Christian Grün <christian.gr...@gmail.com> Sent: Thursday, July 7, 2022 5:27 AM To: Lizzi, Vincent <vincent.li...@taylorandfrancis.com> Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Java 8 and XML Catalog Hi Vincent, XML catalogs and Java 8 are an ungrateful combination indeed. As you know, support for catalogs will improve a lot with BaseX 10, as JDK 11 comes with its own catalog resolver. With BaseX 10, we’ll also support Norm’s XML resolver, as you’ve already discovered (we’ll update our documentation soon). Due to limited resources, we decided to focus on the new version exclusively. It’s interesting to hear, though, that your code is working with BaseX 9 and Java 17. Maybe it’s the inbuilt XML resolver that’s used by Java 17, no matter if an external resolver is added to the classpath? All I can do is guess … Maybe JDK developers would be able to answer that question if we managed to create some self-contained code in Java? Best, Christian
