Saxonica Developer Community

2022-09-28

• 
  Michael Kay Saxon

  23:37 · Commented on issue

  The primary problem I investigated was the heap space problem, this was definitely caused by keeping about 300K XML trees in memory to support the caching of function results. Getting rid of this caching isn't going to make things run fa... Bug #5686: Heap size problems, and crash in TraceListener

  Problem reported by email.
  To be exact, I have two issues tightly related to each other. First of all I have a transformation (step) where for some element nodes an attribute "variant" must be produced with the help of a function (See...
• 
  Michael Kay Saxon

  16:14 · Commented on issue

  How large is the serialized output? Does it work if you serialize to a file or to standard output? Is there memory pressure? Have you looked at a heap dump at the point where it hangs?
  A StringBuffer uses an underlying char[] array so... Bug #5697: Serializing Node to String hangs

  We are using Saxon-EE 9.9.1.8 on Java and we have a problem serialize an Node to a String.
  A transformation on the node is done in 2 minutes. After that, serializing the Node to a String hangs the system.
  Her a section of the stacktrac...

2022-09-27

• 
  Michael Kay SaxonJS

  12:20 · Commented on issue

  I think the "quick fix" is simply to change the code at Expr.js#89 (in my build) from
  ```
  node === m
  ```
  to
  ```
  DU.isSameNode(node, m)
  ```
  (But check for the potential bug identified in comment #9) Bug #5560: intersect doesn’t seem to work correctly for attributes

  While developping XPathle, I stumbled across SaxonJS behaviour that was different than in the Java version.
  Consider the commented-out code at https://github.com/gimsieke/xpathle/blob/main/xpathle-lib.xsl#L184
  If you use the commen...

2022-09-26

• 
  Michael Kay Saxon

  20:34 · Closed issue

  I've reviewed the history here in the course of working on the next Saxon 10 maintenance release, and I don't think it's appropriate to make any further changes in this area, so I'm closing the issue. Bug #4839 (Closed): collection(): failed to parse XML file

  Reported by user on saxon mailing list:
  When the collection() feature is used in the XSLT stylesheet. The following error occurs:
  ~~~
  collection(): failed to parse XML file file:/D:/Test/sample1.xml: I/O error reported by XML pars...
• 
  Michael Kay Saxon

  20:26 · Closed issue

  Closing this in the hope that the version number mismatch is the actual issue. Bug #5096 (Resolved): .NET: FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found

  I'm upgrading Saxon .NET 9.9.1.8 to 10.6. Now, setting the catalog file throws an exception.
  ~~~
  Unhandled Exception: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl, saxon-ee-10.6, V...
• 
  Michael Kay I'm not able to reproduce the problem, which makes it difficult to test a fix.
  However, the code introduced by bug #2305 is still present in DotNetPlatform line 496:
  ```
  System.setProperty("javax.xml.parsers.SAXParserFactory", "or...

  20:14 · Commented on issue
• 
  Michael Kay Saxon

  18:28 · Closed issue

  Bug #5167 (Resolved): Saxon/.NET 10: DocumentBuilder.DtdValidation option has no effect if JAXP parser is used

  Using the Saxon.Api.DocumentBuilder, the option `DocumentBuilder.DtdValidation` has no effect if JAXP parser is used - the document is parsed without validation.
• 
  Michael Kay Confirmed that if we merge features in such a way that a "true" setting always overrides a "false" setting, the unit test now passes.
  The code change applies to the 10.x, 11.x, and 12.x branches even though we have only seen adverse eff...

  18:03 · Commented on issue
• 
  Michael Kay Note that the problem manifests itself as a failure in NUnit test `TestDocumentBuilder.TestSaxSourceValidation()`.

  17:23 · Commented on issue
• 
  Michael Kay Saxon

  10:31 · Closed issue

  For 12.x I have implemented a new command-line option -TPxsl:filename which allows you to supply your own stylesheet for formatting the performance profile. This allows you to output the data in XML or JSON, or to display it more selecti... Feature #5613 (Closed): Saxon-EE profiling HTML not well-formed

  Running Saxon-EE with "-TP" option for profiling produces a not well-formed HTML document. The element /html/head/meta is not terminated with a closing tag.
  I am running Saxon-EE 9.9.1.7 in Oxygen XML Editor 23.1