Subject: Re: [xsl] xsl:function problem From: "Ilya Sterin" <sterini@xxxxxxxxx> Date: Mon, 14 May 2007 08:35:00 -0400 |
Ok, this is really weird, but when I tried to go back and reimplement the function it now validates properly. Leaving the context node based xpath in there produces a correct validation error. I'm not sure what was wrong before, I take it that it was due to the context node access from the function, which wasn't parsed correctly and instead of throwing a context node access exception, instead didn't have function a available in the namespace which produced the function not found error. The weird thing was that the same function validated when no params where used.
> Ah, thanks. I didn't even run the function yet, it fails with a > validation error. But I'll pass the context node as a second param if > I can get the signature to work.
You need to fix the error before you can compile the function. If I run your posted function definition on any inpuit I get:
$ saxon8 func.xsl func.xsl Error on line 7 of file:/c:/tmp/func.xsl: XPDY0002: Cannot select a node here: the context item is undefined Failed to compile stylesheet. 1 error detected.
so saxon doesn't compile this function so there is no function with teh expected signature.
David
________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xsl:function problem, David Carlisle | Thread | RE: [xsl] xsl:function problem, Michael Kay |
Re: [xsl] RE: Replacing the space c, Abel Braaksma | Date | Re: [xsl] RE: Replacing the space c, David Carlisle |
Month |