Project

Profile

Help

Forums » Help »

-p:on command line option: XSLT versus XQuery

Added by Martin Honnen almost 2 years ago

I am not sure I have used the -p:on command line option before but in my attempts today I find that for XSLT something like java -cp 'C:\Program Files\Saxonica\SaxonHE11-5J\saxon-he-11.5.jar' net.sf.saxon.Transform -t -p:on -xsl:strip-space-url-param1.xsl -it works while the same for XQuery java -cp 'C:\Program Files\Saxonica\SaxonHE11-5J\saxon-he-11.5.jar' net.sf.saxon.Query -t -p:on -q:strip-space-url-param1.xq gives an error Static error in query: Exception in ModuleURIResolver::

SaxonJ-HE 11.5 from Saxonica
Java version 11.0.12
Analyzing query from strip-space-url-param1.xq
Static error in query: Exception in ModuleURIResolver:

I get the same error with 12.0 HE and EE. Also with SaxonCS 11.5 query: Exception in ModuleURIResolver: : Object reference not set to an instance of an object.. SaxonCS 12.0, however, seems to be able to handle it.

XQuery and XSLT attached.

Am I misunderstanding the use of the option for XQuery and have to add something more or is there something wrong?

Download all files
strip-space-url-param1.xq (326 Bytes) strip-space-url-param1.xq
strip-space-url-param1.xsl (470 Bytes) strip-space-url-param1.xsl

Replies (3)

Please register to reply

RE: -p:on command line option: XSLT versus XQuery - Added by Norm Tovey-Walsh almost 2 years ago

Any thoughts/opinions on this?

I’m a little confused, actually. The ‘—p:on’ option is documented as
only being supported in PE and EE, so the fact that it appears to work
for XSLT with HE is…possibly an error.

The “exception in ModuleURIResolver” certainly sounds like a bug.

Would you like to file a bug report? If not, I’ll file one so we can
track it.

Be seeing you,
norm

--
Norm Tovey-Walsh
Saxonica

    (1-3/3)

    Please register to reply