First try at 15.beta with eXist 2

[krikrou]

Hi,
I am testing some debug scenario with 15 beta and eXist 2, Saxon-PE 9.5.0.1, enabling xQuery 3.0.

It is great to see that we have much more flexiblity while importing xqm modules!
It seems that there is still a few things that prevents me to run real-world modules (running under eXist):

1 - unknown protocol: java
With this type of declaration :
import module namespace counter = "http://exist-db.org/xquery/counter" at "java:org.exist.xquery.modules.counter.CounterModule";,

I get this error
System ID: oxygen:/eXist$eXist rest/db/es.common/modules/session.xqm
Severity: fatal
Description: XQST0059: java.net.MalformedURLException: unknown protocol: java
Start location: 21:0

Is there a way to enable such java modules ?

2 - eXist xQuery Update extention
This does not seem to be enabled. For instance, something like "update value $item/@is-valid with 'true'" in the code will throw :
System ID: oxygen:/eXist$eXist rest/db/es.common/modules/process-utils.xqm
Severity: fatal
Description: XPST0003: expected ")", found name "value"
Start location: 180:0
URL: http://www.w3.org/TR/xpath20/#ERRXPST0003

3- default modules
prefix for built-in modules (defined in conf.xml) do not need to be declared when runnning code with eXist. Is there a way to allow this under oXygen as well. Actually, I get a lot of 'XPST0081 Prefix ... has not been declared' errors, and would like to avoid having to re-declare them for all modules ; )

That's all for now
Cheers,
C.

[adrian]

Hi,

1. Oxygen works with eXist-db as a remote client, so this may depend on your server configuration. Have you tried running such a module with a different eXist client? I'm guessing the Java Admin Client should behave similarly when used remotely.

2. This worked fine for me. Make sure you're running the query with a scenario that uses the eXist connection as XQuery engine.

3. I'll have to test this. But again make sure you're running the query with the eXist engine. The error seems to be reported by Saxon.

Regards,
Adrian

[krikrou]

Hi Adrian,
Thanks for the answer.

The query runs fine when I apply the associated scenario. However, it seems that I can't find a way to set eXist as the debugger engine:

- when trying to debug an eXist-associated scenario (one for which the Transformer is eXist), I get "The transformer eXist is not available in debugging mode. Using Saxon-PE XQuery" info window.

- No eXist-related engine is listed in the Debugger engine drop-down.

Is there another way to set eXist as the default engine in debugging mode ?

Cheers,
C.

[adrian]

Hi,

So, to clarify, all your previously reported issues were obtained while debugging with Saxon-EE?
Note that enabling XQuery 3.0 support in Saxon disables the XQuery update support.

Currently (v15) there is no support in Oxygen for debugging XQuery with eXist. Obviously, the eXist specific features cannot be debugged with Saxon-HE/PE/EE XQuery.

Regards,
Adrian

LE: We already have a feature request logged on our issue tracking tool to support debugging with eXist in a future version of Oxygen. I've added your vote.

[krikrou]

So, to clarify, all your previously reported issues were obtained while debugging with Saxon-EE?

Yep - seems it is the case. I first thought eXist engine would be enforced.

LE: We already have a feature request logged on our issue tracking tool to support debugging with eXist in a future version of Oxygen. I've added your vote.

Thanks !
C.