Thank you very much, also for the background from the XQuery specification.
Then this solves the issue I encountered.
Best regards,
Johannes
-Ursprüngliche Nachricht-
Von: Christian Grün [mailto:christian.gr...@gmail.com]
Gesendet: Mittwoch, 18. Dezember 2019 18:51
An: Johannes Echterh
> So by creating such an XQuery wrapper module, we would ensure that there is
> only a single import of the Java class (which represents module m1) -
> regardless of how many times the XQuery wrapper module is imported? If so,
> then indeed that sounds like an option.
Exactly: The XQuery specif
Again, thank you, Christian.
So by creating such an XQuery wrapper module, we would ensure that there is
only a single import of the Java class (which represents module m1) -
regardless of how many times the XQuery wrapper module is imported? If so, then
indeed that sounds like an option.
Best
Hi Johannes,
> m1 is a Java module, with de.interactive_instruments.module.MyQueryModule
> being the Java class that extends QueryModule.
> …
> We end up having multiple instances, i.e. Java objects, of class
> MyQueryModule, …
So the solution which I would recommend (and which I would generall
Thank you for your patience and support, Christian.
Then my second question has been answered as well. So basically, when the
XQuery execution involves multiple imports of a Java module, regardless of
packaging, BaseX may create multiple instances of the according Java class.
I slightly updated
> It may also answer my second question, where I was referring to expath
> packaging and if that would make any difference - when compared to having a
> pure JAR with the Java classes (and required libraries). It sounds like
> expath packaging does not make a difference. Please correct me if I g
Hi Christian,
Thank you. If I understand you correctly, that answers my first question.
It may also answer my second question, where I was referring to expath
packaging and if that would make any difference - when compared to having a
pure JAR with the Java classes (and required libraries). It
Hi Johannes,
> · Is it expected behavior that multiple instances of a Java
> QueryModule (M1, in my scenario) may be created and used during an execution
> of a query scenario like the one described above – or in general?
Yes, this is currently expected behavior; the import mechanisms o
On Wed, 2019-12-18 at 11:10 +0530, Sreenivasulu Yadavalli wrote:
> >
> What exactly do you mean by moving collections around?.
>
> A: moving the collections in the same system.
So, you use the Linux "mv" command to do this? Or what?
What exactly do you mean by collections? I for one would find
9 matches
Mail list logo
