Subject: RE: [xsl] param weirdness From: cknell@xxxxxxxxxx Date: Tue, 29 Mar 2005 13:06:00 -0500 |
Do a Google search on "XSLT" and "attribute value template". -- Charles Knell cknell@xxxxxxxxxx - email -----Original Message----- From: Jelks Cabaniss <jelks@xxxxxxxx> Sent: Tue, 29 Mar 2005 12:58:57 -0500 To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: [xsl] param weirdness This *should be* obvious, but sometimes the obvious isn't always to this observer. :) <xsl:call-template name="detail"> <xsl:with-param name="category">markup</xsl:with-param> </xsl:call-template> .. <xsl:template name="detail"> <xsl:param name="category" /> <xsl:for-each select='/config/option[@class="$category"]'> ... </xsl:for-each> </xsl:template> The for-each selects *nothing*, but if I change "$category" to the hard-coded string "markup", it works fine! The `$category` parameter does come through, or so <xsl:value-of select='$category' /> tells me. So why does does a hard-coded category work, while "$category" fails? /Jelks
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] param weirdness, Michael Kay | Thread | [xsl] Strip processing instruction , 04083259 |
[xsl] param weirdness, Jelks Cabaniss | Date | Re: [xsl] param weirdness, Joe Fawcett |
Month |