Problem with replacing string in XSLT

nelly78 · September 15th, 2009, 12:23 PM

Hi All,

I am trying to replace string in XSLT in a .net Application.

Below is the Code how i am trying to replace it :

Template for replacing the String

Code:

 
"<xsl:template name="stringreplace">" 
" <xsl:param name="text"/>" 
" <xsl:param name="replace"/>" 
" <xsl:param name="by"/>" 
" <xsl:choose>" 
" <xsl:when test="contains($text, $replace)">" 
" <xsl:value-of select="substring-before($text,$replace)"/>" 
" <xsl:value-of select="$by"/>" 
" <xsl:call-template name="stringreplace">" 
" <xsl:with-param name="text" select="substring-after($text,$replace)"/>" 
" <xsl:with-param name="replace" select="$replace"/>" 
" <xsl:with-param name="by" select="$by"/>" 
" </xsl:call-template>" 
" </xsl:when>" 
" <xsl:otherwise>" 
" <xsl:value-of select="$text"/>" 
" </xsl:otherwise>" 
" </xsl:choose>" 
"</xsl:template>"

Here i am calling the above template :

Code:

 
<xsl:call-template name="stringreplace">
" <xsl:with-param name="text" select=sAttValue/>
" <xsl:with-param name="replace" select="'</><>'"/>
" <xsl:with-param name="by" select="'|'"/>
" </xsl:call-template>

The value In the variable is sAttValue = " <>3333</><>4444</><>5555</> "

what i am doing is replacing '<></>' with '|' and i am getting remaing string is

<>3333|4444|5555</>.

Now i want want to replace <> and </> with blank value so i vl get

3333|4444|5555

Any Idea How can i do that ?? where can i modify in the template or how to call template again to pass new value for replacing.

Thanks

-Nelly

Martin Honnen · September 15th, 2009, 12:57 PM

You can store the result of calling a template in a variable and then you can use that variable when calling the template again, this time with different parameters:

Code:

<xsl:variable name="s1">
<xsl:call-template name="stringreplace">
  ...
</xsl:variable>
<xsl:variable name="s2">
<xsl:call-template name="stringreplace">
  <xsl:with-param name="text" select="$s1"/>
  <xsl:with-param name="replace" select="'&lt;&gt;'"/>
  <xsl:with-param name="by" select="''"/>
</xsl:call-template>
</xsl:variable>
<xsl:call-template name="stringreplace">
  <xsl:with-param name="text" select="$s2"/>
  <xsl:with-param name="replace" select="'&lt;/&gt;'"/>
  <xsl:with-param name="by" select="''"/>
</xsl:call-template>

On the other hand for simply removing certain characters the translate function suffices:

Code:

<xsl:variable name="s1">
<xsl:call-template name="stringreplace">
  ...
</xsl:variable>
<xsl:value-of select="translate($s1, '&lt;&gt;/', '')"/>

chroniclemaster1 · September 15th, 2009, 11:56 PM

Quote:

Originally Posted by Martin Honnen

You can store the result of calling a template in a variable and then you can use that variable when calling the template again, this time with different parameters:

*sigh* how come this seems so simple when you do it?

nelly78 · September 16th, 2009, 06:56 AM

Hi Martin,

<xsl:variable name=""" & "s2" & """>
<xsl:call-template name=""" & "stringreplace" & """>
<xsl:with-param name=""" & "text" & """ select=""" & sAttValue & """/>
<xsl:with-param name=""" & "replace" & """ select=""" & "'</><>'" & """/>
<xsl:with-param name=""" & "by" & """ select=""" & "'|'" & """/>
</xsl:call-template>
</xsl:variable>

I have tried the above example but it is giving me the below error:

Exception: {0}System.Runtime.InteropServices.COMException (0x80004005):
Variable or parameter 's2' cannot be defined twice within the same template

How can i solve this problem

Thanks
-Nelly

Martin Honnen · September 16th, 2009, 07:05 AM

Well you will need to provide more details if you need help in finding out what causes that error.
Which XSLT processor exactly do you use?
And how does the stylesheet look that causes that error?
And please post the real stylesheet code as XML and not as VB concatenated strings.

nelly78 · September 16th, 2009, 07:41 AM

Hi Martin,

Thanks for your replies. I have found the problem and now its working.

Actually i was calling the template in a loop and same name variable was getting created more than once that was the problem.

Thanks again

-Nelly