Saxonica Developer Community

2020-04-03

• 
  O'Neil Delpratt Saxon/C

  19:06 · Replied in forum

  Dear Thomas,
  Thank you very much for your feedback. We will investigate and address all your points you have raised.
  With 4. Are the schemas you are loading conflicting? The configuration of loading schemas is accumulative, therefo... Saxon/C Help and Discussions: RE: Saxon/C and Windows: several issues with C++ classes

  Hello,
  I am using Saxon/C API 1.2.1 on Windows; first of all: big compliment to all Saxon developers, it is really a nice tool and working stable!
  But I noticed three minor issues here (which I could handle by myself) and one maybe g...

2020-03-30

• 
  O'Neil Delpratt Saxon

  10:36 · Replied in forum

  Thanks for pointing this out to us. I have not committed to the samples directory to subversion. I will look to add the build files too. Help: RE: Is https://dev.saxonica.com/repos/archive/opensource/latest10/samples/ intentionally em...

  Previous releases in the open-source repository included the samples, however, https://dev.saxonica.com/repos/archive/opensource/latest10/samples/ is empty although the Sourceforge resources file has samples.
  Is that directory intent...

2020-03-18

• 
  O'Neil Delpratt Saxon

  10:43 · Closed issue

  Uploaded new maven build with the fix. Bug #4480 (Closed): jline dependency in maven POM file should be optional

  The jline dependency in maven POM file should be optional.
  I will try to change this in the POM file on the current release.
• 
  O'Neil Delpratt The jline dependency in maven POM file should be optional.
  I will try to change this in the POM file on the current release.

  09:59 · Created issue

2020-03-17

• 
  O'Neil Delpratt Saxon

  13:48 · Commented on issue

  Bug fix applied in the Saxon 10 major release. Bug #4478: java.lang.NullPointerException: while trying to invoke the method net.sf.saxon.om.Sequ...

  Hi Colleagues,
  While consuming SaxonEE 9.9.1.6 version in SAP, our customer is facing issues while XSLT processing.
  I've attached the payload and the xslt file, along with the detailed error traces.
  FYI: We are noticing this issue...
• 
  O'Neil Delpratt Saxon

  13:48 · Commented on issue

  Bug fix applied in the Saxon 10 major release. Bug #4476: Type error evaluating (fn:collection(...))

  I get a type error if I make a transformation using the following stylesheet ans Saxon 9.9.1.7.
  It works with Saxon 9.9.1.5 and 9.9.1.6.
  I think is related with: https://saxonica.plan.io/issues/2749
  ~~~ xml
  <xsl:stylesheet xmlns:xsl=...
• 
  O'Neil Delpratt Saxon

  13:48 · Commented on issue

  Bug fix applied in the Saxon 10 major release. Bug #4475: collection() fails java.util.concurrent.ExecutionException: java.lang.NegativeArraySi...

  Reported by email.
  A call on collection() that worked in 9.9.1.6 is failing with 9.9.1.7. Repro supplied.
• 
  O'Neil Delpratt Saxon

  13:48 · Commented on issue

  Bug fix applied in the Saxon 10 major release. Bug #3202: --multipleSchemaImports has no effect when processing a cycle of schema documents

  The configuration flag --multipleSchemaImports changes Saxon's behaviour when a schemadoc A imports B and C, and B and C have the same target namespace. However it has no effect when A imports B and B imports C, and A and C have the same...
• 
  O'Neil Delpratt Saxon

  13:47 · Closed issue

  Bug fix applied in the Saxon 10.0 major release. Bug #4340 (Closed): Performance degraded after moving from Saxon 8.9 to 9.8.0.15 (use case Enterp...

  Customer upgraded to the latest version of our product which uses Saxon 9.8.0.15 EE.
  They came from an older version which used Saxon 8.9.0.14.
  They process thousands of documents per day with hundreds of XSLs.
  For two use cases (see ...
• 
  O'Neil Delpratt Saxon

  13:47 · Closed issue

  Bug fix applied in the Saxon 10.0 major release. Bug #2820 (Closed): Location information locks source stylesheet tree into memory

  Not confirmed, but from looking at the code, when we compile an instruction, e.g. XSLElement.compile(), we set location information on the compiled instruction by calling StyleElement.allocateLocation(), and this uses the StyleElement it...