• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
  • Getting Started with XSLT
  • Tutorial: Understanding How Templates Work
  • Working with Stylesheets
  • Creating Stylesheets That Generate HTML
  • Specifying Extension Functions in Stylesheets
  • Working with Templates
  • Using Third-Party XSLT Processors
  • Validating Result Documents
  • Post-processing Result Documents
  • Generating Formatting Objects
  • Generating Scalable Vector Graphics
  • Generating Java Code for XSLT
  • XSLT Instructions Quick Reference
    • xsl:apply-imports
    • xsl:apply-templates
    • xsl:attribute
    • xsl:attribute-set
    • xsl:call-template
    • xsl:character-map
    • xsl:choose
    • xsl:comment
    • xsl:copy
    • xsl:copy-of
    • xsl:decimal-format
    • xsl:element
    • xsl:fallback
    • xsl:for-each
    • xsl:for-each-group
    • xsl:function
    • xsl:if
    • xsl:import
    • xsl:import-schema
    • xsl:include
    • xsl:key
    • xsl:message
    • xsl:namespace-alias
    • xsl:number
    • xsl:otherwise
    • xsl:output
    • xsl:output-character
    • xsl:param
    • xsl:preserve-space
    • xsl:processing-instruction
    • xsl:sequence
    • xsl:sort
    • xsl:strip-space
    • xsl:stylesheet
    • xsl:template
      • Format
      • Description
    • xsl:text
    • xsl:transform
    • xsl:value-of
    • xsl:variable
    • xsl:when
    • xsl:with-param
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Integrating with Third-Party File Systems
• Chapter 14: Extending Stylus Studio
• Chapter 15: The Stylus Studio Java API
• Chapter 16: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > xsl:template

xsl:template

Specifies a template rule.

Format

<xsl:template 
               
  [match = "pattern"]
               
  [name = "qname"] 
               
  [mode = "mode"] 
               
  [priority = "priority"]>
               
  template_body
               
</xsl:template>
               

            

Description

The match attribute is required except when you specify the name attribute. The pattern you specify for the match attribute identifies the source node or set of source nodes to which the template rule applies.

The optional name attribute specifies a name for the template. You can use the name of a template to invoke it with the xsl:call-template instruction. The value you specify for name must be a qualified name. If you specify a name attribute, a match attribute is not required.

The optional mode attribute prevents the template from matching nodes selected by an xsl:apply-templates instruction that specifies a different mode. The value of mode must be a qualified name or an asterisk ( *). If you specify an asterisk, it means match any node.

If an xsl:apply-templates instruction contains a mode attribute, the xsl:apply-templates instruction can apply to only those xsl:template instructions that specify a mode attribute with the same value. If an xsl:apply-templates instruction does not contain a mode attribute, the xsl:apply-templates instruction can apply to only those xsl:template instructions that do not specify a mode attribute.

If you specify the match and mode attributes, they have no effect if the template is instantiated by the xsl:call-template instruction. If you specify the name attribute, you can still instantiate the template as a result of an xsl:apply-templates instruction.

If two or more templates have the same name, Stylus Studio uses the template that appears last in the stylesheet.

The template body contains literal results and XSLT instructions. The XSLT processor instantiates the template body for each node identified by pattern. This means the XSLT processor copies literal results to the result document and executes the XSLT instructions.

If there is more than one matching template rule, the XSLT processor chooses the matching template rule with the higher priority. If both have the same priority, the XSLT processor chooses the one that occurs last in the stylesheet.

For examples and additional information about templates, see Working with Templates.