Subject: [xsl] alternative to msxsl:node-set($variable) From: "Paul Thomas" <pthomas@xxxxxxxxxxxxxxx> Date: Wed, 10 Jan 2001 21:19:34 +0530 |
Hi all, I've been searching all over the place for a way to handle our problem, and I can't find one. I hope someone on the list can help. From what I've seen, it looks like using "msxsl:node-set($variable)" is what we need, but our product is stuck with the May 2000 msxml parser, so we can't use it. We'll upgrade the parser eventually, but we can't do it now... What we want to do is this: 1. A user clicks on an html link to request something. Based on which link was clicked, we store an xpath expression in an xml element node, i.e. <ActionPath>Challenges/Incontrol/AspectNode/ActionNode[Action/@ID=21]</Actio nPath> 2. Later, we retrieve that path into a variable and use it in an xpath expression in order to show what the user wanted to see. e.g. <xsl:variable name="ActionPathVar" select="ActionPath"/> <xsl:for-each select="$ActionPathVar"> [show the stuff the user wanted...] </xsl:for-each> It seems like our problem is that we've got a result tree fragment in our ActionPathVar when what we need is a node-set. That much I think I've figured out from previous posts. But I haven't found a workaround to this that doesn't use a node-set() function. Any ideas would be much appreciated. Thanks a lot. Paul XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Summing computed values, Jeni Tennison | Thread | Re: [xsl] alternative to msxsl:node, David Carlisle |
[xsl] Summing computed values, Lorenzo De Sio | Date | RE: [xsl] Summing computed values, Clapham, Paul |
Month |