Saxonica Developer Community

Today

• 
  Michael Kay Saxon

  11:37 · Edited issue

  Starting with the fn-contains-token and fn-contains test sets in QT4, I've added some new tests (suffixed -dyn) that modify existing tests by using external variables in place of literals in the query. Bug #4976 (In Progress): Inadequate bytecode testing: unfolded option on empty sequence

  Many of the W3C test cases can be defeated by an optimiser that does early evaluation: for example all the starts-with tests in which one of the operands is an empty sequence actually write the operand as "()", which means there are no t...
• 
  Michael Kay Saxon

  10:48 · Edited issue

  Bug #4982 (AwaitingInfo): Loading xml schemas which are stored inside a zip archive is very slow compared to Xerces

  We have an in-house application which, prior to processing an xml document, validates it against the xml schema. The xml schemas are stored in zip archives, which we obtain "out of band" from associated parties. We make the schemas avail...

2021-05-12

• 
  Michael Kay Saxon

  20:22 · Closed issue

  The location information used to be set in StyleElement.makeTraceInstruction(), which still exists in vestigial form although it no longer does anything useful. I think we can probably fix it by repurposing (and renaming) this method, si... Bug #4970 (Resolved): line/column number in trace listener

  Line and column numbers obtained in Saxon 9.9.1.8 trace listener:
  ~~~
  $ cat in.xml
  <?xml version="1.0" encoding="UTF-8"?>
  <iron weight="1" />
  $ java -jar ${SAXON_JAR} -s:in.xml -xsl:'https://github.com/xspec/xspec/raw/v2.0.7/tutor...
• 
  Michael Kay It seems there was a change in design for tracing in 10.x - instead of wrapping each expression/instruction in a TraceExpression as it is created, we post process the compiled code adding trace expressions into the tree on completion. Th...

  19:56 · Commented on issue
• 
  Michael Kay Saxon

  18:34 · Closed issue

  Added a JUnit test `NamespaceMapTest.testIncrementalRemove()` which demonstrates the bug and shows that the suggested fix works. Bug #4971 (Resolved): Deleting an entry from NamespaceMap can cause IndexOutOfBoundsException

  The code at NamespaceMap.put() reads
  ~~~
  n2.prefixes = new String[prefixes.length - 1];
  System.arraycopy(prefixes, 0, n2.prefixes, 0,position);
  System.arraycopy(prefixes, position+1, ...
• 
  Michael Kay Saxon

  18:19 · Closed issue

  I completed the integration of XQuery Update tests into the QT4 test suite. The multi-phase tests are handled by allowing the `<test-case>` element to contain a sequence of `test` elements: the second and subsequent queries take the outp... Bug #4972 (Resolved): XQuery Update testing

  It appears that our routine automated testing does not exercise the XQuery Update test suite.
  It's especially unclear what the status is of XQuery Update testing on .NET
• 
  Michael Kay Saxon

  18:12 · Closed issue

  I have changed `Controller.warning()` so that it tolerates any of the three arguments (message, errorCode, location) being null. Bug #4975 (Resolved): Null pointer exception when XSLT 3.0 run from the command line

  in oXygen (<oXygen/> XML Editor 23.1, build 2021040908) with the 10.3 external add-on, the transform (small.xsl) works. oXygen 23 uses a Java 15 JRE
  
  17:40 bin % ./java --version
  openjdk 15.0.1 2020-10-20
  OpenJDK Runtime Environmen...
• 
  Michael Kay Saxon

  18:05 · Closed issue

  Bug #4985 (Resolved): NullPointerException in Saxon-EE

  I get an NullPointerException when i run the attached stylesheet in Saxon-EE, latest version.
  Saxon-HE gives no NullPointerException.
  The stylesheet is part of the XSLT 3.0 Test Suite:
  ..\xslt30-test-b42c1b89b44f\report\viewer\p...
• 
  Michael Kay The solution is for `TextValueTemplateNode.parse()` to catch any error thrown by the call on `AttributeValueTemplate.make()`, and report it via `StyleElement.compileError()`, rather than letting it bubble upwards causing the processing o...

  17:53 · Commented on issue
• 
  Michael Kay For reasons which I don't understand, the error in the text-value-template at line 41 (specifically, the call on ixsl:query-params) is causing the `prepare-attributes` phase of processing on template main to be abandoned, meaning that wh...

  17:14 · Edited issue