RE: [xsl] Losing xsl:param values within a called template for-ea ch loop

Subject: RE: [xsl] Losing xsl:param values within a called template for-ea ch loop
From: "CROFT, MICHAEL" <MCROFT@xxxxxxxxx>
Date: Mon, 13 May 2002 19:01:22 -0400
I removed the quotes, I get the same results.  What Im trying to achieve is
almost a nested template (which is currently illegal), ideally I would like
to do this...

<xsl:template name=command>
	<xsl:template match="COMMAND">
		//process descendants of COMMAND

Only when I encounter a certain condition do I want to call the named
template, and process the <COMMAND> elements descendants with xsl:param's
Ive passed...

How can I best achieve this logic since I there are no nested templates...

-----Original Message-----
From: J.Pietschmann [mailto:j3322ptm@xxxxxxxx]
Sent: Monday, May 13, 2002 6:33 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Losing xsl:param values within a called template
for-each loop

>	<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
> xsl:template element, and still cycle through the specific <KeyGroup>
> elements for the parent <COMMAND> element?  Any help is greatly

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 match="command"/>


 XSL-List info and archive:

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender and postmaster@xxxxxxxxxx

 XSL-List info and archive:

Current Thread