Well, as i said in the first post, is possible that the number of vars will grow
to a number i do not know at this time...
So maybe i'm thinking too "procedural" but it seems that having 100 for-each
loops to assign 100 vars is much more time- and resources-consuming than having
only one for-each loop doing all the assignments.
And, as i said to Michael Kay, i have to use XSLT 1.0 . The message for Michael
was intended to go to the list, but i'm stuck with this stupid webmail program
that messes all the reply-to's addresses...
Sorry for that.
Quoting David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk>:
What i want is to have a variable to use outside the <xsl:for-each> loop,
as a
attribute
<xsl:if test="$pages!=''">
<Event method="nextPage" target="btnProceed" type="ActionHandler">
<xsl:attribute name="next"><xsl:value-of select="$pages"
/></xsl:attribute>
<xsl:attribute name="params"><xsl:value-of select="$params"
/></xsl:attribute>
</Event>
</xsl:if>
as a concatenation of all the strings i've found.
Quoting David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk>:
well for that, you want the for-each inside the variable declaration as
you showed in your other piece of code. What was the problem with that?
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--
O SAPO já está livre de vírus com a Panda Software, fique você também!
Clique em: http://antivirus.sapo.pt