There's no need for all the complexity of variable passing. The
template that you are calling is fully contextualized as though the
code where in the place where the call is made. Your named template
that you call can access @jdbc-type itself, don't pass a param.
I realize I didn't exactly answer, but hopefully that will help.
simon
On Thursday, January 9, 2003, at 01:03 AM, Anthony Kong wrote:
<xsl:variable name="java_type">
<xsl:call-template name="translate_type">
<xsl:with-param name="db_type" select="@jdbc-type"/>
</xsl:call-template>
</xsl:variable>
I intended (wish, actually :-) to capture the result into variable
"java_type". However it failed.
What is a better way to achieve this?
---
www.simonwoodside.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list