Saxonica Developer Community

2024-07-10

• 
  Michael Kay Saxon

  12:09 · Closed issue

  Committed an improvement to the Javadoc on the 12.x branch; no code change. Bug #6476 (Resolved): XPathParser.parseNamespaceTest()

  This bug may be symptomless - I encountered it during development of Saxon 13 and I don't know if the relevant code is executed in previous releases.
  `XPathParser.makeNamespaceTest()` contains the code:
  ```
  if (prefix.star...
• 
  Michael Kay On investigation, it seems that in 12.x the string passed as prefix is actually in the form `Q{uri}*` including the trailing `*`, so -2 is correct. I hit the problem in 13.x because I was calling it without the trailing `*`.

  11:55 · Commented on issue
• 
  Michael Kay This bug may be symptomless - I encountered it during development of Saxon 13 and I don't know if the relevant code is executed in previous releases.
  `XPathParser.makeNamespaceTest()` contains the code:
  ```
  if (prefix.star...

  10:37 · Closed issue

2024-07-08

• 
  Michael Kay Saxon

  23:35 · Replied in forum

  >how can I obtain the running Transformation
  You seem to be asking for some magic here whereby Saxon somehow knows who "you" are and calls your code without the actual program running the stylesheet asking it to do so. That seems a bi... Open Discussion: RE: Altering a Saxon-EE User's Configuration Within Custom Extension Code After Transform Start

  Hello Once Again,
  I have had my head in the Saxon Javadocs, and I see several methods related to setting a whole configuration (e.g. *Configuration.instantiateConfiguration*), with some described as customization hooks (e.g. *Transfor...
• 
  Michael Kay >In other words, after a user starts a transform involving my extension classes and functions (whether via oXygen or the command line or wherever), I want to grab the current configuration from the running transform, alter it to register...

  09:08 · Replied in forum
• 
  Michael Kay Saxon

  23:27 · Commented on issue

  Thanks for reporting it.
  I can see where it's going wrong: in `ForEachGroup` it is doing
  ```
  expr.makeSortKeyEvaluators();
  ```
  during the first-time-through code without checking that the sort options are constants. Bug #6472: Sort order not recognised for xsl:for-each-group in named template (Saxon HE 12.xJ)

  I have an issue setting the sort order for xsl:for-each-group via a xsl:param inside a named template.
  When I call the same template more than once it seems to remember the sort order from the first call.
  The first call to the templa...

2024-07-07

• 
  Michael Kay Saxon

  21:16 · Created issue

  Bug #6473 (New): Expression `/[x]` is not accepted

  The expression `/[x,y]` is apparently legal in XPath 3.1 -- it should be interpreted as the path `/` (selecting the root node) followed by an array constructor evaluated with that root node as the context item. (One might imagine an alte...
• 
  Michael Kay Saxon

  11:26 · Replied in forum

  The `for (AtomicValue key : keys.next()) {` looks wrong...
  And you could perhaps shave off a couple of microseconds by doing
  ```
  for (KeyValuePair kvp : metadataMap.keyValuePairs()) {
  metadata.addUserMetadata(kvp.key.getStringVa... Open Discussion: RE: Handling Map Parameters Passed to Custom Extension Instructions: Questions re Types

  Hello All,
  Whilst writing my custom extension function (Java-based), I expected to follow the following model for my call method
  ``` java
  public class MyExtensionFunction extends ExtensionFunctionDefinition {
  @Override
  ...

2024-07-06

• 
  Michael Kay Saxon

  15:32 · Replied in forum

  It's an excellent question and I don't think I know the answer.
  Even with the built-in internal functions, there are now so many of them that we have had to think hard about the cost of initialising a data structure to hold details of... Open Discussion: RE: Saxon Configuration to Recognize Java Extension Functions and Elements : Best Approaches

  Hello,
  Here is my situation in a nutshell:
  I am developing dozens, *potentially hundreds* of Saxon extension functions and elements. I am doing so in Eclipse and oXygen, and for now, am adding lines to the Saxon config file as I g...
• 
  Michael Kay Saxon

  09:24 · Replied in forum

  Saxon has two layers of API, which we might call the system programming interface (SPI) and the application programming interface (API - specifically, for Java, s9api). When you write deeply embedded code like integrated extension functi... Open Discussion: RE: Handling Map Parameters Passed to Custom Extension Instructions: Questions re Types

  Hello All,
  Whilst writing my custom extension function (Java-based), I expected to follow the following model for my call method
  ``` java
  public class MyExtensionFunction extends ExtensionFunctionDefinition {
  @Override
  ...