alexandrev-tibco
53e90ef86e
Full coverage of XSLT 1.0, 2.0 and 3.0 elements and XPath functions: - 59 XSLT elements (xsl:stylesheet → xsl:use-accumulators) - 170 XPath functions (1.0 node/string/numeric/boolean, 2.0 sequence/ date/QName/string, 3.0 HOF/map/array/JSON/streaming) Each page: description, parameters table, return value, 2 runnable Saxon examples with input XML + stylesheet + output, notes, cross-links. xsltCompletions.js: all 229 entries now have blogSlug for hover links. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.7 KiB
title, description, date, version, versionLabel, category, syntax, tags
| title | description | date | version | versionLabel | category | syntax | tags | |||
|---|---|---|---|---|---|---|---|---|---|---|
| xsl:next-match | Applies the next-priority matching template rule for the current node, passing optional parameters and tunnel parameters. | 2026-04-18T00:00:00Z | 2.0 | XSLT 2.0 | element | <xsl:next-match/> |
|
Description
xsl:next-match fires the next template rule that would have matched the current node if the current template rule did not exist. It is the XSLT 2.0 successor to xsl:apply-imports, but works across all templates regardless of import precedence — not only imported ones.
The "next" template is determined by priority order: templates are ranked by import precedence and then by specificity. xsl:next-match skips the currently executing template and invokes the one immediately below it in that ranking. If no further matching template exists, the built-in default rules apply.
This enables clean decorator-style patterns: a high-priority template handles a special case and then delegates the bulk of processing to a more generic rule.
Parameters
xsl:next-match has no attributes. It may contain:
| Child element | Description |
|---|---|
xsl:with-param |
Passes a parameter to the next template. |
xsl:fallback |
Fallback content for processors that do not support xsl:next-match. |
Return value
The result produced by the next matching template rule, inserted into the current output.
Examples
Adding a wrapper around generic output
Input XML:
<?xml version="1.0" encoding="UTF-8"?>
<doc>
<para role="highlight">Important note.</para>
<para>Regular paragraph.</para>
</doc>
Stylesheet:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes"/>
<!-- Generic rule: all para elements -->
<xsl:template match="para">
<p><xsl:apply-templates/></p>
</xsl:template>
<!-- Specific rule: highlighted para — wraps the generic output -->
<xsl:template match="para[@role='highlight']" priority="2">
<div class="highlight">
<xsl:next-match/>
</div>
</xsl:template>
<xsl:template match="doc">
<body><xsl:apply-templates/></body>
</xsl:template>
</xsl:stylesheet>
Output:
<body>
<div class="highlight"><p>Important note.</p></div>
<p>Regular paragraph.</p>
</body>
Passing a parameter to the next template
Stylesheet:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="item" priority="2">
<!-- Do something extra, then delegate -->
<xsl:next-match>
<xsl:with-param name="class" select="'special'"/>
</xsl:next-match>
</xsl:template>
<xsl:template match="item">
<xsl:param name="class" select="'normal'"/>
<entry class="{$class}"><xsl:value-of select="."/></entry>
</xsl:template>
</xsl:stylesheet>
Notes
xsl:next-matchdiffers fromxsl:apply-importsin that it considers all lower-priority templates, not only those from imported stylesheets.- It may only be used inside a template rule (
xsl:template). Using it insidexsl:functionis an error. - If no further matching template exists, the built-in template rule for the node type applies (e.g., text nodes produce their string value, element nodes apply templates to children).
- Tunnel parameters passed with
xsl:with-param tunnel="yes"flow transparently through the entire call chain.