Hot to access principalResult of the transformation? [saxonJS]

Question

I migrate from saxon-CE to saxonJS (v1.2.0)

The output of the XSLT transformation need to be captured as an XML Document object as it was in saxon-CE:

var xslPath = './*.xsl';
var xsl = Saxon.requestXML(xslPath);
var proc = Saxon.newXSLT20Processor(xsl);
var xmlDoc;
var xmlDocTransformed;
var xmlStr;

xmlDoc = Saxon.parseXML(app.getLoadedMEI());
xmlDocTransformed = proc.transformToDocument(xmlDoc);

It tried to apply SaxonJS this way:

var result;
result = SaxonJS.transform({
         stylesheetLocation: "./*.sef.xml",
         sourceLocation: "./*.xml",
         destination: "application"
      });

and expected to get a transformation results object where I can access the principalResult property as described in the official documentation (#destination) and in this presentation.

When running the code I obtain the following:

There is no problem with transformation itself: when destination is set to replaceBody it works as expected.

Answer 1

One way is, of course, to use the fn:transform function with "normal" XSLT code:

const xml = `<root>
  <item>a</item>
</root>`;

const xslt = `<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  version="3.0"
  xmlns:xs="http://www.w3.org/2001/XMLSchema"
  exclude-result-prefixes="#all"
  expand-text="yes">

  <xsl:output method="xml"/>

  <xsl:mode on-no-match="shallow-copy"/>

  <xsl:template match="/" name="xsl:initial-template">
    <xsl:next-match/>
    <xsl:comment>Run with {system-property('xsl:product-name')} {system-property('xsl:product-version')} {system-property('Q{http://saxon.sf.net/}platform')}</xsl:comment>
  </xsl:template>

</xsl:stylesheet>`;

const resultString = SaxonJS.XPath.evaluate(`transform(map { 'source-node' : parse-xml($xml), 'stylesheet-text' : $xslt, 'delivery-format' : 'serialized' })?output`, null, { params : { 'xml' : xml, 'xslt' : xslt } });

console.log(resultString);

<script src="https://martin-honnen.github.io/Saxon-JS-2.3/SaxonJS2.js"></script>

Not recommended for performance reason but perhaps a workaround that avoid the hassle of creating an SEF. If you want to create an SEF, note, that the Node.js xslt3 tool from Saxonica can also do that, you don't need a current version of Saxon EE, just xslt3 -t -export:my-sheet.sef.json -nogo -xsl:my-sheet.xsl.

Answer 2

Eventually I solved my task with the following code (Saxon JS 2.3):

var options = {
        stylesheetLocation: xslPath,
        sourceText: inputXmlStr,
        stylesheetParams: params,
        destination: "document"
    };

    var result = SaxonJS.transform(options);
    var transformedXmlStr = SaxonJS.serialize(result.principalResult);

The SEF could be produced by xslt3 tool. Note that you might use the alternative command for this (windows 10 power shell):

node node_modules/xslt3/xslt3.js "-t" "-xsl:stylesheet.xsl" "-export:stylesheet.sef.json" "-nogo"