<xsl:variable name="nset">
<xsl:copy-of select="/campus[(_at_)name = $value]"/>
</xsl:variable>
as has been said already in thi sthread, don't (ever) do that, which
generates a result tree fragment (and is expensive even in XSLt2 where
it would generate a node set)
do
<xsl:variable name="nset" select="/campus[(_at_)name = $value]"/>
However there will only be one element node below / so thi snode set
will have at most one element in it, depending on whether the top level
element is a campus element with that attribute. Is that really what you
want?
and then define the template match = "campus". But
wouldn't
<xsl:template match="campus"> match other campus nodes as well.
It would match, but unless you apply templates to those other nodes,
they would never be processed.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. 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>
--~--