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).
Well, we can keep the existing extension and see if someone uses it.
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.
Thanks, I see. However, I'd like to ask again, because my question was mostly about the fact that a local URI resolver instance will not be known by a remote BaseX instance. See the following example:
Context context = new Context(); context.setURIResolver(...); ClientSession session = ... ClientQuery query = session.query(...); query.next();
Here, the specified URI resolver would not be known to the addressed server instance, as this one will be a remote BaseX instance, or at least one in a different JVM.
Cheers, Christian