Hi Christian,
On 24/04/2015 12:36, Christian Grün wrote:
Hi Karel,
It might be problem for our production code, because we all different kinds of sessions (ClientSession, LocalSession, StreamingLocalSession).
I see. Maybe we could try another thing and add a new option [1] named URIRESOLVER with a fully-qualified class name as value (similar to Saxon's flag -mr)?
I am definitely for this one, however I would like for this not to be only option, because you are limited by no-argument constructor instantiation of the resolver + you have to specify this at start of JVM. Sometimes this isn't flexible enough (however I think it is sufficient enough for our usecase).
And one question, out of interest: As the URI resolver only works with LocalSession instances, how do you tackle the problem with ClientSession instances?
We just started with idea of splitting xquery into multiple modules. So far all our production code runs on single (huge) xquery files.
So far I created workaround tool, that extracts all xquery source files from classpath directory to temporary directory and then set org.basex.QUERYPATH to that directory. It is non-invasive and so far works in all enviroments and cases, however we would obviously prefer better sollution for production.
Karel
Best, Christian