Bug #4588
closedxsl:initial-template seems to be executed by fn:transform called from SaxonJS.XPath.evaluate although options set initial-match-selection and global-context-item
100%
Description
I am trying to call fn:transform
from XPath, providing the result of a parse-json
call as both the initial-match-selection
and the global-context-item
.
When the XSLT used has an xsl:template match="."
, the template seems to be applied using apply-templates, however, when the template additionally has xsl:template match="." name="xsl:initial-template"
, the template is executed but I get an error about the focus being absent.
With the Java version of Saxon it appears that my combination of options to fn:transform
always results in the expected apply-templates invocation, I think Saxon-JS 2's behaviour is a bug.
Javascript code showing the error is
require('saxon-js');
const xslt = `<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:map="http://www.w3.org/2005/xpath-functions/map"
exclude-result-prefixes="#all"
expand-text="yes">
<xsl:output method="adaptive"/>
<xsl:template match="." name="xsl:initial-template">
<result>
<xsl:comment>Run with {system-property('xsl:product-name')} {system-property('xsl:product-version')}</xsl:comment>
<xsl:sequence select="."/>
</result>
</xsl:template>
</xsl:stylesheet>`;
const json = `[1, 2, 3]`;
function transform(input, xslt, inputType, resultsSelect) {
var transformationResult;
if (inputType === 'XML') {
transformationResult = SaxonJS.XPath.evaluate(
"transform(map {'stylesheet-text': $stylesheet-text , 'source-node' : parse-xml($source-text), 'delivery-format' : 'serialized' })",
[],
{
params: {
'stylesheet-text': xslt,
'source-text': input
}
}
);
}
else if (inputType === 'JSON') {
transformationResult = SaxonJS.XPath.evaluate(
"let $json-input := parse-json($json-input-string) return transform(map {'stylesheet-text': $stylesheet-text , 'global-context-item' : $json-input, 'initial-match-selection' : $json-input, 'delivery-format' : 'serialized' })",
[],
{
params: {
'stylesheet-text': xslt,
'json-input-string': input
}
}
);
}
else if (inputType === 'None') {
transformationResult = SaxonJS.XPath.evaluate(
"transform(map {'stylesheet-text': $stylesheet-text, 'delivery-format' : 'serialized' })",
[],
{
params: {
'stylesheet-text': xslt
}
}
);
}
console.log(transformationResult);
}
transform(json, xslt, 'JSON', null);
while a change of the inlined XSLT to
const xslt = `<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:map="http://www.w3.org/2005/xpath-functions/map"
exclude-result-prefixes="#all"
expand-text="yes">
<xsl:output method="adaptive"/>
<xsl:template match=".">
<result>
<xsl:comment>Run with {system-property('xsl:product-name')} {system-property('xsl:product-version')}</xsl:comment>
<xsl:sequence select="."/>
</result>
</xsl:template>
</xsl:stylesheet>`;
works as expected, the passed in XDM array is the context item in the template.
The error I get is
message: 'Focus for . (dot) is absent',
code: 'XPDY0002',
xsltLineNr: '14',
which I assume indicates that call template invocation on xsl:initial-template
is done. As I said, with the same fn:transform
options and Saxon Java I don't get any interference by the name="xsl:initial-template"
attribute, both XSLT versions use apply templates.
Updated by Michael Kay over 4 years ago
- Assignee set to John Lumley
- Priority changed from Low to Normal
Updated by John Lumley over 4 years ago
- Status changed from New to Resolved
- Applies to JS Branch Trunk added
It turns out that in internalTransform()
, call-template mode was being chosen when there was name="xsl:initial-template"
present, checking only for the absence of (the internal forms of) a source-node
, not that and initial-match-selection
. Simple patch fixes this.
Updated by Community Admin almost 4 years ago
- Applies to JS Branch 2 added
- Applies to JS Branch deleted (
2.0, Trunk)
Updated by Debbie Lockett almost 4 years ago
- Fix Committed on JS Branch 2 added
- Fix Committed on JS Branch deleted (
Trunk)
Updated by Debbie Lockett almost 4 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to Saxon-JS 2.1
Bug fix applied in the Saxon-JS 2.1 maintenance release.
Please register to edit this issue
Also available in: Atom PDF Tracking page