Hi, Marco...
Use of extension functions - particularly user-defined extension functions - in XSLT is inherently not portable. It wasn't very helpful of me to point out that using ExpressionContext wouldn't be portable. Sorry about that. I don't have any suggestions for a portable means of defining extensions functions.
A portable way of doing something like this is to use a custom URIResolver. Send some string as the href to the resolver's resolve method (i.e. <xsl:value-of select="document('something')/result"/>) identifying what you want. Then in your resolve method return it as XML.
best, -Rob
Thanks,
Henry ------------------------------------------------------------------ Henry Zongaro Xalan development IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044 mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
