In case this is helpful, here are examples of code I've written to use an XML
catalog with xslt:transform(). These examples were slightly modified to put
into an email so there might be some typos.
Version 1:
In this example the XML document "file.xml" might be coming from a zip file or
other
Hello Christian, Gerrit, Liam, Graydon,
Is it possible to use a different XML Catalog Resolver with BaseX? I'm
referring specifically to the new XML resolver that Norm Tovey-Wash presented
today at Declarative Amsterdam. The presentation recording is at
Hi James,
Sounds like a good hint! I’ll be happy to have a look at your pull request.
Thanks in advance,
Christian
On Fri, Nov 5, 2021 at 1:20 PM James Ball wrote:
>
> Hi Christian,
>
> My Google-fu was definitely letting me down. I completely missed that POST
> and PUT had to be explicitly
> Adding the path to Saxon to a shell environment variable CLASSPATH didn't
> work.
I assume that this variable won’t be evaluated anywhere. You could
have a look into the basex startup script in order to see what’s
happening.
Or are you only working with the standalone basex.jar file?
> It
With BaseX 10, which will be based on JDK 11, we’ll switch to the
built-in JDK Catalog Resolver [1], which tends to get good reviews,
and which allows for a much cleaner and more consistent integration.
Debugging should be easier as well, as errors will always be reported
back if the catalog
Hi Christian,
My Google-fu was definitely letting me down. I completely missed that POST and
PUT had to be explicitly included.
Thank you for the snapshot - which I’ve downloaded and tried. Sadly - same
error.
I *think* I’ve found yet another default configuration for GZIPHandler getting
in
On 05.11.2021 03:03, Liam R. E. Quin wrote:
On Thu, 2021-11-04 at 18:43 -0400, Graydon Saunders wrote:
Related to this, setting the catalog for use by xslt:transform() is
defeating me.
The only ways i have found to debug these are
(1) with strace -f, to make sure the file is being read
7 matches
Mail list logo
