|
Subject: Re: [xsl] accessing last element of node set passed as parameter From: Joerg Heinicke <joerg.heinicke@xxxxxx> Date: Tue, 21 May 2002 21:15:11 +0200 |
<xsl:variable name="tmp">
<xsl:copy-of select="$result"/>
<BAR i="{$i}"/>
</xsl:variable>
<xsl:apply-templates select="following-sibling::*[1]">
<xsl:with-param name="result" select="xalan:nodeset($tmp)"/>
</xsl:apply-templates>Thanks David! Some of this is starting to click ... but then again something happens that shuts the clicker down.
Since order is important to me, I decided to heed your warning about the ordering of a union being implementation dependent, so I set about making all of the "BAR" elements be siblings of one another. I replaced:
<xsl:apply-templates select="following-sibling::*[1]">
<xsl:with-param name="result" select="$result|xalan:nodeset($new)"/>
</xsl:apply-templates> </xsl:template>
with:
<xsl:apply-templates select="following-sibling::*[1]">
<xsl:with-param name="result">
<xsl:copy-of select="$result"/>
<BAR i="{$i}"/>
</xsl:with-param>
</xsl:apply-templates> </xsl:template>
but now I get the following error message:
Can not convert #RTREEFRAG to a NodeList!
at the line:
<xsl:copy-of select="($result/BAR)[last()]" />
the first time the "A" template is matched with a non-empty value for "result". Shouldn't "result" be a node set?
Paul (I think this language is going to make my head explode)
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] accessing last element of, paul morgan | Thread | Re: [xsl] accessing last element of, paul morgan |
| Re: [xsl] accessing last element of, paul morgan | Date | Re: [xsl] accessing last element of, paul morgan |
| Month |