This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Position of a result tree fragment
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Position of a result tree fragment
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Thu, 19 Jul 2001 03:20:03 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
A result tree fragment does not have a parent.
Mike Kay
Software AG
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Laurence O
> Garfield
> Sent: 19 July 2001 00:08
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] Position of a result tree fragment
>
>
> If I am passing a result tree fragment from one template to
> another using
> a variable, is there any way to determine what the fragment's position
> within its parent was originally? According to the XSLT spec
> I can't use
> /, //, or [] on result tree fragments, so I can't use
> [position()]. Is
> there some other way, or do I have to pass the position of the node
> through as a second variable as well?
>
> --Larry Garfield
> lgarfiel@students.depaul.edu
>
> DePaul Linux Users Group Secretary
>
> -- "If at first you don't succeed, skydiving isn't for you." :-)
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list