This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re[4]: finding position() of an element in a different context
- To: Michael Kay <xsl-list at lists dot mulberrytech dot com>
- Subject: Re[4]: [xsl] finding position() of an element in a different context
- From: Kevin Burges <xmldude at burieddreams dot com>
- Date: Wed, 2 May 2001 16:57:06 +0100
- Organization: burieddreams.com
- References: <002001c0ce34$fda40520$0100007f@PCUKMKA>
- Reply-To: xsl-list at lists dot mulberrytech dot com
Sorry for not getting back to this earlier, I've been away for a fe
days...
>> Am I not right in saying that if I am in the context of a <visit>
>> element, doing:
>>
>> <xsl:variable name="matchingForm"
>> select="//forms/form[(@formtypeID = $formtypeID) and (@visitID =
>> $visitID)]"/>
>>
>> will not work, because "//forms" is taken relative to the context
>> node? Certainly this seems to be happening, as no matches are
>> occurring.
MK> //forms selects all the <forms> elements in the same document as the context
MK> node.
That is what I was hoping for.
MK> Your problem is more likely to be your attribute names: your <visit> element
MK> has an @id attribute but no @visitID attribute; similarly there is no
MK> @formtypeID.
I noticed that as well, but it was just a type when creating the email
I think. That problem is not present in the actual code I'm using (on
a different computer). I will take a look back at what I was doing and
once I've got my head around it again I'll post back...
--
groovy baby,
Kevin mailto:xmldude@burieddreams.com
++++++++++++ Cool music - http://mp3.com/marshan
++++++ Attitude Webzine - http://burieddreams.com/attitude
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list