Re: [basex-talk] specifying the processor for xslt:transform()

On Thu, 2021-11-04 at 18:43 -0400, Graydon Saunders wrote: > Hi Christian -- > > > It will probably be the case that I'm going to want to run the > transform > with either Saxon-EE or Saxon-PE when both are available.  My memory of the code is that BaseX keeps a cache of compiled stylesheets;

Re: [basex-talk] specifying the processor for xslt:transform()

Hi Christian -- Adding the path to Saxon to a shell environment variable CLASSPATH didn't work. There was no pre-existing CLASSPATH, so I suspect the current Fedora Java setup is doing something clever somewhere, and I'd have to go comprehend it. Since I expect to be deploying this particular

Re: [basex-talk] Content-Encoding: gzip on incoming RESTXQ POST

Hi James, This is due to the default gzip settings of Jetty, which exclude POST requests. There had been a similar question in the past, and I have now decided to add the POST and PUT method to the Jetty defaults [1,2]. A new snapshot is available! Cheers, Christian [1]

Re: [basex-talk] specifying the processor for xslt:transform()

Hi Graydon, > I can get xslt:transform() to pick up a licensed saxon if I go into the > appropriate script (basexgui, etc.) and add it to the class path there. (but > not, oddly, from the environment class path on Linux.) That's going to be > annoying as BaseX updates with laudable frequency.