Re: [basex-talk] Basex xquery import module classpath lookup

Exactly, I am refering to import module. In my experience with xml-related technologies and java, library usually supports customizable class for import resource lookup based on namespaces, paths etc, I can recall 2 examples: Saxon has class ModuleURIResolver that does just this:

Re: [basex-talk] Basex xquery import module classpath lookup

I would like to load xquery files that are on classpath of my java application, not only filesystem. Does this mean, it is not possible with BaseX? Do you refer to the import module when talking about loading xquery files? The classpath is not considered when importing modules. As multiple

Re: [basex-talk] Basex xquery import module classpath lookup

Thanks for the links. If I get it right, you need to explicitly call the URI resolver setter functions to get it working? Or does it mean that modules will automatically be available via import module if they are in the Java classpath (which is, if I got it right, the feature you asked for)? On

Re: [basex-talk] Basex xquery import module classpath lookup

Thanks Christian, I read trough that wiki and as far as I understand it, is all about relative path on filesystem. I would like to load xquery files that are on classpath of my java application, not only filesystem. Does this mean, it is not possible with BaseX? Karel On 08/04/2015 18:01,

Re: [basex-talk] Bug? Local variable has not been allocated a stack frame slot

Bummer, it's very tricky to isolate/repro in a minimal case. At the moment don't have the time to pursue this further. Maybe later. --Marc On Wed, Apr 8, 2015 at 2:27 PM, Marc van Grootel marc.van.groo...@gmail.com wrote: Sure, I'm going to try this evening. If it's indeed Saxon we would

Re: [basex-talk] Basex xquery import module classpath lookup

We always use custom URIResolver when working with classpath resources afaik. Similar mechanism might be better than original feature for reasons you stated (duplicity in classpath). You can solve this by choosing correct classloader in *URIResolver. I've been digging a little into BaseX