A template can match from a selection of location paths, individual paths being separated with "|". : template « XSLT stylesheet « XML Tutorial






File: Data.xml
<?xml version="1.0" encoding="utf-8"?>

<employee>
  <firstName>Joe</firstName>
  <surname>Smith</surname>
</employee>

File: Transform.xslt

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

  <xsl:template match="firstName|surname">
    <div>
      <xsl:text>[template: </xsl:text>
      <xsl:value-of select="name()" />
      <xsl:text> outputs </xsl:text>
      <xsl:apply-templates />
      <xsl:text> ]</xsl:text>
    </div>
  </xsl:template>
</xsl:stylesheet>

Output:

<?xml version="1.0" encoding="UTF-8"?>
  <div>[template: firstName outputs Joe ]</div>
  <div>[template: surname outputs Smith ]</div>








5.67.template
5.67.1.xsl:template match="/"
5.67.2.Call template based function recursively
5.67.3.match=county[starts-with(.,K)]
5.67.4.template match=state priority=2
5.67.5.without if
5.67.6.Template with parameters
5.67.7.Mark a parameter as requred
5.67.8.While XSLT does not define while and for loops, their behavior can be simulated.
5.67.9.A template can match from a selection of location paths, individual paths being separated with "|".
5.67.10.This priority order can be specified with the priority attributte.
5.67.11.the default action in the absence of priority attributes.
5.67.12.With modes an element can be processed multiple times, each time producing a different result.
5.67.13.Parts of XML document to which template should be applied are determined by location paths
5.67.14.Processing always starts with the template match="/"
5.67.15.When a template for the node exists, there is no default processing invoked
5.67.16.If you want to include descendants of the node, you have to explicitly request their templates.