I heavily use Novell IDM if you haven't noticed from my other blog articles. Recently, I needed to use Novell IDM to do a global find/replace. Typically, this can be done in policy very quickly by just replacing all instances of a character with another character (or series of characters).
I hit an issue where the characters that I was doing the replacement with were special characters in the context of the IDM, so they were not output correctly. In order to get the replacement done correctly, I needed to do it in the Output Transformation policy so they didn't get fubar'd while passing the text around.
So, what I did was make an XSL Template to do a global find/replace, then call the function. I was pretty proud of my code, its pretty elegant the way it was implemented.
<xsl:template name="globalReplace">
<xsl:param name="outputString"/>
<xsl:param name="target"/>
<xsl:param name="replacement"/>
<xsl:choose>
<xsl:when test="contains($outputString,$target)">
<xsl:value-of select="concat(substring-before($outputString,$target),$replacement)"/>
<xsl:call-template name="globalReplace">
<xsl:with-param name="outputString" select="substring-after($outputString,$target)"/>
<xsl:with-param name="target" select="$target"/>
<xsl:with-param name="replacement" select="$replacement"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$outputString"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
So, we pass this function our information. If the target isn't present, it just throws back the string unmodified. If the target is present, it takes the substring up to that string, tacks on the replacement, then recursively calls itself until all replacements are done.
Nice little piece of code for XSL to hold on to.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment