Saxon

I've started by running this on 9.9 and I get a different error:

Error in xsl:copy-of/@select on line 10 column 29 of Relationship_EBI.xsl:
  XPDY0002: The context item is absent
at procedure setEnrichedMessage on line 9 of Relationship_EBI.xsl:
     invoked by global xsl:variable
  In template rule with match="/" on line 13 of Relationship_EBI.xsl

This is because the global variable contains a reference to the global context item ".", and StreamingTransformerFactory explicitly doesn't allow that: the Javadoc for StreamingTransformerFactory states: "Because it is designed for streaming, the source document does not become the global context item (specifically, if a global variable references the value of the context item ".", a dynamic error XPDY0002 occurs)."

So on 9.9, this is working as designed.

I have reproduced the error you are seeing on the 9.8 branch.

Although the Javadoc for StreamingTransformerImpl in 9.8 states the same restriction on use of the context item as in 9.9, it does not seem to be enforced as rigorously; in fact, on the non-streaming path being executed, the context item is explicitly set to the source node of the transformation. And in fact, this doesn't seem to be related to the failure, because we get the same failure if we substitute an EnterpriseTransformerFactory for the StreamingTransformerFactory.

What actually seems to be happening here is that the input document contains whitespace text nodes. The element causing the failure is:

<test>
	<a>12
3</a>
	<b>456</b>
</test>

which fails because text() selects more than one child text node (there are three whitespace text node children).

The stylesheet specifies xsl:strip-space so this shouldn't be happening

The idea of the customer was to replace &#xA and &#xD with a semicolon.

Their main argument is that this works fine on commandline and not in the way we apply the XSL.

There seems to be a clear error on the 9.8 branch that has been corrected in 9.9. In Controller.makeSourceTree(), 9.8 has

if (config.isStripsAllWhiteSpace() || isStylesheetContainingStripSpace() ||
                validationMode == Validation.STRICT || validationMode == Validation.LAX) {
            Stripper stripper = makeStripper(sourceBuilder);
            spaceStrippingRule = stripper.getSpaceStrippingRule();
        }

which has been changed in 9.9 to

if (config.isStripsAllWhiteSpace() || isStylesheetContainingStripSpace() ||
                validationMode == Validation.STRICT || validationMode == Validation.LAX) {
            r = makeStripper(sourceBuilder);
            spaceStrippingRule = getSpaceStrippingRule();
        }

So 9.8 is creating the stripper (which does the whitespace stripping) but isn't inserting it into the document-building pipeline.

Looking at the change history, 9.9 has had this change since it was first released.

The error appears to have been introduced into the 9.8 branch with commit 2588, which was attempting to fix bug 3885, and first hit the field with maintenance release 9.8.0.15.

Also confirmed that the test works on 9.9 if we change the StreamingTransformerFactory to an EnterpriseTransformerFactory.

(I also had to delete inactive code using an old MessageEmitter interface to get it to compile under 9.9)

Confirmed also that the method in question (Controller.makeSourceTree()) is not being used when the transformation is run from the command line. For some reason the command line has its own way of doing the source document building, which differs from the code used by JAXP.

As workaround for our customer: Is there a XSL level change that we can do to get this XSL working the way it does on commandline?

I think at the XSLT level the simplest is probably to strip whitespace text nodes explicitly:

<xsl:mode name="strip-space" on-no-match="shallow-copy"/>
<xsl:template match="text()[.='']" mode="strip-space"/>
<xsl:function name="f:strip-space" as="document-node()">
  <xsl:param name="in" as="document-node()"/>
  <xsl:apply-templates select="$in" mode="strip-space"/.
<xsl:function>

Sorry I don't get how to use this. The function is not invoked from what I see. And the requirement is to replace the and whitespace characters with ';' (semicolon). This is part of the Cleanup.xsl

You're currently doing:

	<!-- Perform Enrichments -->
	<xsl:variable name="setEnrichedMessage">
		<xsl:copy-of select="." />
	</xsl:variable>

	<xsl:template match="/">
		<!-- Perform Clean Up -->
		<xsl:apply-templates select="$setEnrichedMessage" mode="CleanUp"/>
	</xsl:template>

I'm not sure I understand the logic of this (why is setEnrichedMessage a copy of the input document, why can't it use the original? Perhaps there's some overriding stylesheet somewhere?) but as written you could simply change the logic to

<xsl:apply-templates select="f:strip-space(.)" mode="CleanUp"/>

or you could change the variable to

        <xsl:variable name="setEnrichedMessage">
		<xsl:apply-templates select="." mode="strip-space" />
	</xsl:variable>

If the aim is to replace those two characters in text nodes then I would simply match on text() and perform the replacement e.g. instead of

	<xsl:template match="*[text()[contains(.,'&#xA;') or contains(.,'&#xD;')]]" mode="CleanUp">
		<xsl:copy>
			<xsl:apply-templates select="@*" mode="CleanUp"/>
			<xsl:value-of select="replace(replace(text(),'&#xA;',';'),'&#xD;',';')"/>
		</xsl:copy>
	</xsl:template>

you could simply use

        <xsl:template match="text()" mode="CleanUp">
            <xsl:value-of select="replace(replace(.,'&#xA;',';'),'&#xD;',';')"/>
        </xsl:template>

As you already have an identity transformation template the element node copying is taken care of.