RE: [xsl] Data Integration at runtime using XSL

[<Ambika.Das@xxxxxxxxxxxxxxxxxx>]

Hi Jim,

Given below is the code.

<xsl:template name="add_symbol_to_output">

     <xsl:param name="symbol_param"/>
      <xsl:choose>
        <xsl:when test="contains($symbol_param,'|')">
          <xsl:value-of
    		select="substring-before($symbol_param,'|')"/>
        </xsl:when>
        <xsl:otherwise>
          <xsl:value-of select="$ symbol_param "/>
        </xsl:otherwise>
      </xsl:choose>

    </xsl:template>

<xsl:for-each select="parent/child">

 	<xsl:variable name="inputParam" select="$inputSymbol"/>

  	<xsl:call-template name="add_symbol_to_output">
              	<xsl:with-param name=" symbol_param "
select="$inputParam"/>
  	</xsl:call-template>

Thanks & Regards,
Ambika Prasad Das


-----Original Message-----
From: James Fuller [mailto:jim.fuller@xxxxxxxxxxxxxx]
Sent: Thursday, September 07, 2006 3:14 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Data Integration at runtime using XSL

Ambika.Das@xxxxxxxxxxxxxxxxxx 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



DISCLAIMER:
This message contains privileged and confidential information and is intended
only for the individual named.If you are not the intended recipient you should
not disseminate,distribute,store,print, copy or deliver this message.Please
notify the sender immediately by e-mail if you have received this e-mail by
mistake and delete this e-mail from your system.E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain
viruses.The sender therefore does not accept liability for any errors or
omissions in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard-copy version.