Why don't you use XSLT for implementing the upperCase function. This works
always with all XSLT processors and you don't have to mess with extension
functions.
e.g.
StringUtils.xsl
<xsl:template name="upperCase">
...
</xsl:template>
Main.xsl
<xsl:include href="StringUtils.xsl"/>
<xsl:call-template name="upperCase">
<xsl:with param name="$mystring"/>
</xsl:call-template>
I agree it's not easy to implement all string functions, but for easy ones
like this I think it's an advantage to use templates instead of extension
functions.
Kind regards,
Ismaël
-----Original Message-----
From: Laura [mailto:xsl_list(_at_)hotmail(_dot_)com]
Sent: vrijdag 17 januari 2003 12:30
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] calling extension java functions. ( Saxon Vs Xalan)
I have a java extension method that i call from my XSL
the way i call is
<xsl:value-of select="str-utils:upperCase($mystring)"/>
it works fine with Xalan but fails with Saxon.
saxon gives
Transform failed: At xsl:value-of on line 264 of
file:/tests/saxon-test.xsl: No method matching upperCase with 1 parameter
found in class com.myutils.util.StringUtils
the namespace declaration is:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xmlns:saxon="http://icl.com/saxon"; xmlns:str-utils =
"com.myutils.utils.StringUtils"
extension-element-prefixes="saxon str-utils" version="1.0">
It however doesnt give any error with the Xalan ( with a different namespace
declaration)
Am i calling it correctly?? is there any difference in the way you call
extension functions with xalan and saxon?
Thanks
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list