Musings

I recently answered a question on a popular programmers forum about how to store and access an array of user-defined variables in a stylesheet and then loop though those variables.  I realized that many developers are not familar with the available techniques for doing this and decided to add an entry in my blog about this topic.

User-defined variable arrays within stylesheets are not part of the XSLT specification.  The usual way to handle this problem in XSLT 1.0 stylesheets is to define a user-defined top-level element which belongs to a non-null namespace which is different from the XSLT namspace.  These user-defined top-level elements are typically used to store error messages, lookup data, etc.  You can then access these user-defined elements from within your stylesheet by treating the stylesheet as an additional source document and loading it using the document() function with an empty string as the first argument.  An empty string is interpreted to mean the current stylesheet.

The following stylesheet demonstrates this method. <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:foo="http://foo.com" exclude-result-prefixes="foo"> <xsl:output method="text" encoding="utf-8"/> <foo:vars> <foo:var name="z1">A</foo:var> <foo:var name="z2">B</foo:var> <foo:var name="z3">C</foo:var> <foo:var name="z4">D</foo:var> </foo:vars> <xsl:template match="/"> <xsl:for-each select="document(”)/xsl:stylesheet/foo:vars/foo:var" > <xsl:value-of select="." /> <xsl:if test="position() != last()"> <xsl:text>,</xsl:text> </xsl:if> </xsl:for-each> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet>

If you are using XSLT 2.0, this method is no longer needed as simpler and more elegant methods are available to us.  For example, you can store and directly access the variables using the <xsl:variable> element as shown in the following stylesheet. <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" > <xsl:output method="text" encoding="utf-8"/> <xsl:variable name="z1" select="’A'" /> <xsl:variable name="z2" select="’B'" /> <xsl:variable name="z3" select="’C'" /> <xsl:variable name="z4" select="’D'" /> <xsl:variable name="vars" select="$z1, $z2, $z3, $z4" /> <xsl:template match="/"> <xsl:for-each select="$vars" > <xsl:value-of select="." /> <xsl:if test="position() != last()"> <xsl:text>,</xsl:text> </xsl:if> </xsl:for-each> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet>

Another way to store and access this data in a XSLT 2.0 stylesheet is to use a global variable definition as shown below. <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" > <xsl:output method="text" encoding="utf-8"/> <xsl:variable name="vars"> <var name="z1">A</var> <var name="z2">B</var> <var name="z3">C</var> <var name="z4">D</var> </xsl:variable> <xsl:template match="/"> <xsl:for-each select="$vars/var" > <xsl:value-of select="." /> <xsl:if test="position() != last()"> <xsl:text>,</xsl:text> </xsl:if> </xsl:for-each> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet>

All three stylesheets output the same data.

You may be wondering about this image.  It is from the screen of my laptop.  I used xsltproc on Microsoft Vista SUA for the XSLT 1.0 transformation and Saxon 9 in Microsoft Powershell v2.0 CTP2 for the two XSLT 2.0 transformations.

Note that the