Hi Jim,
Given below is the code.
<xsl:for-each select="parent/child">
<xsl:variable name="nCnt" select="position()"/>
<xsl:text>,</xsl:text>
<xsl:value-of
select="fid[(_at_)id='FIELD_1']"/>
<xsl:text>,</xsl:text>
The template for tokenizing the input parameter is as follows
<xsl:param name="input_param"/>
<xsl:choose>
<xsl:when test="contains($input_param,'|')">
<xsl:value-of
select="substring-before($input_param,'|')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$ input_param "/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
Let me know if you require any other details.
Thanks & Regards,
Ambika Prasad Das
-----Original Message-----
From: James Fuller [mailto:jim(_dot_)fuller(_at_)ruminate(_dot_)co(_dot_)uk]
Sent: Thursday, September 07, 2006 3:14 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Data Integration at runtime using XSL
Ambika(_dot_)Das(_at_)iflexsolutions(_dot_)com wrote:
For example, if the symbol list is abc|def, the first row should have
abc as symbol header and the second row should have def as the header.
We are able to tokenize the strings, but fitting the result to the
correct rpw in the for-each loop is the issue.
would be very helpful if u posted a small (but representative) xml and
xslt to illustrate your problem.
the use of for-each is the constraint here.
gl, Jim Fuller
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--