Saxonica Developer Community

2023-11-14

• 
  Philip Fearon Saxon

  14:51 · Commented on issue

  Thanks for the feedback on the sample code. The code the sample is based on is quite dated because it's just used for one rather obscure feature, so needs an overhaul anyway. Bug #6236: Expected XPathException but got AssertionError 'No current component'

  With Saxon 10.9 and Saxon 12.0, (HE or PE) , with the attached (new-context.zip) Java and XSLT we get an AssertionError instead of the expected XPathException which was thrown in previous Saxon versions (10.5 for example). Here is the ou...

2023-10-31

• 
  Philip Fearon Saxon

  16:33 · Closed issue

  Bug #6236 (Closed): Expected XPathException but got AssertionError 'No current component'

  With Saxon 10.9 and Saxon 12.0, (HE or PE) , with the attached (new-context.zip) Java and XSLT we get an AssertionError instead of the expected XPathException which was thrown in previous Saxon versions (10.5 for example). Here is the ou...

2023-08-15

• 
  Philip Fearon Saxon

  21:39 · Commented on issue

  For changing the context node, do these count also?
  xsl:copy with @select
  xsl:perform-sort
  xsl:merge-source
  xsl:source-document
  Support #6170: Which XSLT instructions actually change the context-node before processing the children?

  I am looking for all the XSLT instructions that actually change the context-node before processing the children.
  According to [[https://www.w3.org/TR/xslt-30/#additional-dynamic-context]] , these are all the elements and attributes:
  ...

2023-02-06

• 
  Philip Fearon Saxon

  21:48 · Replied in forum

  The lack of a TextEmitter option in the command line interface is no longer critical for me.
  For VSCode use, I've coded a simple set of classes (targeting different Saxon versions)
  extending net.sf.saxon.Transform and overriding newT... Open Discussion: RE: XSLT command-line option '-m' - 'From Saxon 11.1 this option has no effect.'

  
  The Saxon 12 docs for the XSLT command-line options state that, for the '-m' option: 'From Saxon 11.1 this option has no effect.'
  I used to frequently use this option on the command line as follows:
  ```
  -m:net.sf.saxon.serializ...

2023-01-28

• 
  Philip Fearon Saxon

  09:48 · Posted in forum

  
  The Saxon 12 docs for the XSLT command-line options state that, for the '-m' option: 'From Saxon 11.1 this option has no effect.'
  I used to frequently use this option on the command line as follows:
  ```
  -m:net.sf.saxon.serializ... Open Discussion: XSLT command-line option '-m' - 'From Saxon 11.1 this option has no effect.'

  
  The Saxon 12 docs for the XSLT command-line options state that, for the '-m' option: 'From Saxon 11.1 this option has no effect.'
  I used to frequently use this option on the command line as follows:
  ```
  -m:net.sf.saxon.serializ...

2023-01-16

• 
  Philip Fearon Saxon

  16:34 · Closed issue

  Bug #5823 (Closed): The implemented fn:slice function signature differs from the Saxonica docs and the specification

  Using the attached XSLT 4.0 - with extensions enabled - with SaxonJ 12.0 PE:
  When running the attached XSLT (test.xsl) from the command-line against itself I get the following error:
  ```
  Error in xsl:variable/@select on line 9 col...

2022-01-08

• 
  Philip Fearon SaxonJS

  11:37 · Closed issue

  Bug #5198 (Closed): NodeJS run from command-line with '-it:main' arg results in error when using mode="#current"

  
  This fails with SaxonJS 2.3 but the same XSLT runs OK using the Java version of Saxon. Here is the SaxonJS standard output:
  ~~~
  Saxon-JS
  2.3
  ==== Watch Variables ====
  doc: books
  
  Transformation failure: TypeE...

2021-05-20

• 
  Philip Fearon Saxon

  11:20 · Closed issue

  Bug #4996 (Closed): Namespace information missing from default XML Schema attribute added by validating XMLReader

  This issue is present in Saxon 10.5 but not in Saxon 9.8 or Saxon 9.9. It appears to be related to [issue 4993](https://saxonica.plan.io/issues/4993?issue_count=25&issue_position=3&next_issue_id=4992&prev_issue_id=4994)
  This case (sou...

2021-05-19

• 
  Philip Fearon Saxon

  12:54 · Commented on issue

  I'm checking for an inconsistency at the moment. For parsing the lexical XML, we extend `org.xml.sax.helpers.XMLFilterImpl` to gather lexical information that would otherwise be discarded by the parser. We are seeing another test failure... Bug #4993: java.lang.IllegalStateException: Prefix is bound to the wrong namespace {http://www.deltaxml.com/ns/mini-xhtml}

  This exception is thrown in Saxon 10.5 by an XSLT transform deep within our product's Java filter-chain class.
  The XML source file ([`00-2]-dxml-whitespaceDetection.xml`) for the transform (attached) has a root element in the default na...

2021-05-18

• 
  Philip Fearon Saxon

  14:49 · Commented on issue

  OK thanks, with your comment on the `-ea` switch, I understand better now why I couldn't reproduce this error outside of our TestNG environment.
  Our main objective is to ensure the tests pass with Saxon 10.n. I don't yet know quite ho... Bug #4993: java.lang.IllegalStateException: Prefix is bound to the wrong namespace {http://www.deltaxml.com/ns/mini-xhtml}

  This exception is thrown in Saxon 10.5 by an XSLT transform deep within our product's Java filter-chain class.
  The XML source file ([`00-2]-dxml-whitespaceDetection.xml`) for the transform (attached) has a root element in the default na...