Saxonica Developer Community

2023-06-08

• 
  Michael Kay Saxon

  01:12 · Replied in forum

  I've raised an issue regarding this message at https://saxonica.plan.io/issues/6068
  It's complicated because of the number of different APIs for invoking validation, including the ability to invoke validation from XSLT and XQuery (in ... Help: RE: Suppress std err output during Schema validation

  Hi there.
  I'm performing XML Schema validation using Saxon-EE 11.5.0.0. I'm using the s9api and my own `InvalidityHandler` to capture errors. If a document being validated has a schema violation, then a message is always being output ...
• 
  Michael Kay Saxon

  01:08 · Created issue

  Bug #6068 (New): The "NNN validation errors were reported" message.

  See https://saxonica.plan.io/boards/3/topics/9433
  If a validation episode finds one or more invalidities, then at the end of validation, several things may happen:
  (a) A summary message of the form `Error on line 1 column 60
  XQ...

2023-06-07

• 
  Michael Kay Saxon

  22:32 · Closed issue

  Once reproduced, it was easily solved: simply checking for a null return from `evaluator.eval()` in `Elaborator.elaborateForString()`. Bug #6067 (Resolved): NullPointerException with upper-case function

  On Saxon-HE 12.2 from Java,
  XML document:
  ``` xml
  <L2 id="1"/>
  ```
  XPath:
  ``` xml
  //*[contains(upper-case(@f1), "a")]
  ```
  Saxon gave unexpected exception:
  ``` shell
  java.lang.NullPointerException: Cannot invoke "Object....
• 
  Michael Kay Now reproduced in the debugger. There was a trivial difference in the way the source document was referenced, which may have resulted in the query running in push mode rather than pull mode.

  21:34 · Commented on issue
• 
  Michael Kay I noticed that from the command line I was running Java 11.0.6, from IntelliJ I was running Java 17. Reconfigured IntelliJ to use 11.0.6. No difference, still no failure.

  20:15 · Commented on issue
• 
  Michael Kay I checked out the 12_2 tag from the repo, which should be exactly the code we used to build 12.2, and ran this again in IntelliJ: again, no failure.
  But then I rebuilt the HE jar files from this source, and ran from the command line, ...

  20:07 · Commented on issue
• 
  Michael Kay Although I can reproduce the problem running Saxon-HE 12.2 from the command line, I have built an IntelliJ project over the Saxon-HE source code and the problem does not occur.
  Actually, I built this over the current source code which...

  19:29 · Commented on issue
• 
  Michael Kay Thanks for reporting it. It's failing in Saxon-HE but not in -EE.
  In fact it doesn't crash in -EE even with -opt:0, or when run without a license file.

  16:59 · Commented on issue
• 
  Michael Kay Saxon

  15:42 · Commented on issue

  An expression using the "=" operator is called a General Comparison, and the rules are found at
  https://www.w3.org/TR/xpath-31/#id-general-comparisons
  To summarise, if you compare `S = T` when S and T are sequences, the comparison ... Bug #6051: Bug on exist() with non-existing attribute

  Maybe that's interesting:
  https://github.com/BaseXdb/basex/issues/2212
• 
  Michael Kay I agree with Martin's analysis.
  Note however that if XPath 1.0 compatibility mode is enabled, comparing an empty sequence to `false()` returns true, whereas without 1.0 compatibility mode, it returns false. Of course an XPath 1.0 proc...

  13:13 · Commented on issue