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.
It's possible that the way your environment is configured, you're only
seeing the last error message. Just speculating, but it's possible that the
first message said the code of the function was invalid because of the
context reference, and the second message said that the function didn't
exist (which would be a spurious error caused by the function being
invalid.) How are you running the transformation, and (if you can reproduce
it) what exactly did the error output look like?
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--