This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Losing xsl:param values within a called template for-eachloop
- From: "J.Pietschmann" <j3322ptm at yahoo dot de>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Tue, 14 May 2002 00:32:51 +0200
- Subject: Re: [xsl] Losing xsl:param values within a called template for-eachloop
- References: <CF698667C737D41198E50060943F3CF6F681D7@hoexch03.amica.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
CROFT, MICHAEL wrote:
> <!-- LOSING THE PARAM VALUES HERE-->
> <xsl:if test="@refid = '$keyid'">
You are comparing the value of the @refid attribute with
the literal string '$keyid', not with the value assigned
to the keyid parameter. Remove the quotes.
> Also, Im not sure how to avoid using the name & match attributes in the same
> xsl:template element, and still cycle through the specific <KeyGroup>
> elements for the parent <COMMAND> element? Any help is greatly appreciated.
I'm not sure what you want to achieve but your template
matching COMMAND is an elaborate noop unless you pass
non-empty keyvalue and keyid parameters in an apply-template
you haven't shown us.
You can always split them:
<xsl:template name="command">
...
</xsl:template>
<xsl:template match="command"/>
J.Pietschmann
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list