Re: [xsl] Using sibling value in streaming mode

Subject: Re: [xsl] Using sibling value in streaming mode
From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 30 Aug 2019 21:49:26 -0000
On 30.08.2019 23:18, Martynas JuseviD
ius martynas@xxxxxxxxxxxxx wrote:

The value of <string key="id"> is used as <id> in <item> elements. The
problem is that <string key="id"> can occur in any position in the

I've tried using an accumulator such as

<xsl:accumulator name="map-id" initial-value="()" streamable="yes"
    <xsl:accumulator-rule match="/array/map/string[@key = 'id']/text()"

and then

     <id><xsl:value-of select="accumulator-before('map-id')"/></id>

That worked partially -- only for sibling <string> elements that
followed the <string key="id">. Which is not surprising.

I've also tried accumulator-after('map-id') but got:

   XTSE3430: Template rule is not streamable
   * A call to accumulator-after() is consuming when there are no
preceding consuming instructions

Is it possible to have a streaming solution in this case?

How large are the maps? Can't you afford to switch to "normal"
processing with e.g.

<xsl:template match="map">
  <xsl:apply-templates select="copy-of()" mode="non-streaming"/>

<xsl:template match="map" mode="non-streaming">
    <xsl:apply-templates select="string[not(@key = 'id')]" mode="#current">
      <xsl:with-param name="id" select="string[@key = 'id']"/>

<xsl:template match="string" mode="non-streaming">
  <xsl:param name="id"/>
  <item xsl:expand-text="yes">


Some buffering will be needed, converting the whole XML map structure in
an XPath 3.1 map stored in an accumulator might also work.

Current Thread