This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Evaluating parameter in <xsl:when> vs evaluating parameter in <xsl:sort>
- From: roelf at exinet dot co dot za (Roelf Jansen)
- To: xsl-list <xsl-list at lists dot mulberrytech dot com>
- Date: Thu, 25 Jul 2002 08:59:49 +0200
- Subject: [xsl] Evaluating parameter in <xsl:when> vs evaluating parameter in <xsl:sort>
- Organization: Exinet
- Reply-to: xsl-list at lists dot mulberrytech dot com
Thanks to everyone who responded..
The solution turned out to be:
..
<xsl:when test="$sortParameter='name'" >
<xsl:for-each select="query">
<xsl:sort select="xalan:evaluate($sortParameter)"
order="ascending"/>
Inside the loop I can get hold of the value simply again (just a test
in this case - I don't need the value here):
<xsl:copy-of select="$sortParameter"/>
...
At all occurences of '$sortParameter' I'm looking for its string value
ie 'name' (or 'date' or 'status').
Why is it that in the <when> & <copy> tags I can call it simply but in
the sort tag it needs the xalan:evaluate() ?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list