xsl---
<xsl:template name="a">
  <xsl:param name="href" />
  <xsl:param name="text" />
  <a href="{$href}" onClick="showData('{$href}');return
false;"><xsl:value-of select="$text" /></a>
</xsl:template>
<xsl:template match="/">
  <xsl:call-template name="a">
      <xsl:with-param name="href" select="'process.asp'" />
      <xsl:with-param name="text" select="'Click me, baby'" />
  </xsl:call-template>
</xsl:template>
--
output----
<a href="process.asp" onClick="showData('process.asp');return
false;">Click me, baby</a>
------

I have no obstacles except its length. exslt:function seems like it
would suffice. Reading up now.

Could you provide a short working example that exactly shows what it
does in your current situation, an example of the source, plus a
specification of the processor and where you use it (browser based, PI,
commandline, from java etc) and if you provide any parameters externally?

Now we are only guessing on how to optimize your code...

Steve wrote:
> No, not context. Passed manually...