RE: Msxml4 node-set and Filters bug

Yes, thank you very much. This worked..

>your for-each has moved you into the node set  generated from the
result
>tree fragment, this has its own root node and that xpath is taken
> relative to that, not relative to the original document.

Good, I get it now.. So no errors/bugs in msxml4.. But a small error in
my knowledge of xslt... 8-) 

Regards
Henk meulekamp.

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of David
Carlisle
Sent: maandag 11 november 2002 13:38
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Msxml4 node-set and Filters bug



<xsl:value-of select="/root/data/COURSE/RESULT[@IDLEARNINGOBJECT=
$lo]/@CLEARNINGOBJECT"/>

your for-each has moved you into the node set  generated from teh result
tree fragment, this has its own root node and that xpath is taken
relative to that, not relative to the original document.


instead do

<xsl:variable name="originaldoc" select="/"/><xsl:for-each
   select="msxsl:node-set($learningobjects)/learningobjects/lo">....
<xsl:value-ofselect="$originaldoc/root/data/COURSE/RESULT......


David

PS
<xsl:element name="lo"><xsl:attribute
name="id"><xsl:value-of select="@IDLEARNINGOBJECT"/></xsl:attribute>
					<xsl:attribute
name="cname"><xsl:value-of select="@CLEARNINGOBJECT"/> </xsl:element>

is a very long winded way of writing

<lo id="{@IDLEARNINGOBJECT}" cname="{@CLEARNINGOBJECT}"/>

which is totally equivalent.

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list