Subject:How is SS handling unknown extension functions? Author:Richard Wagenknecht Date:25 Sep 2001 10:17 AM
The XSL I'm working on will ultimately be processed by MSXML. As such, I have to convert result tree fragments to node sets using the msxsl:node-set extension function. Curiously, if I leave these function calls inside my XSL file, SS seems to ignore them and just continue on (since SS is implementing the 1.1 XSL functionality of allowing result tree fragments to be used as node sets).
Is this correct behavior and can I count on this continuing?
Subject:Re: How is SS handling unknown extension functions? Author:Minollo I. Date:25 Sep 2001 10:25 AM
>The XSL I'm working on will ultimately be processed by MSXML. As such, I
>have to convert result tree fragments to node sets using the
>msxsl:node-set extension function. Curiously, if I leave these function
>calls inside my XSL file, SS seems to ignore them and just continue on
>(since SS is implementing the 1.1 XSL functionality of allowing result
>tree fragments to be used as node sets)
Stylus Studio supports msxsl:node-set and it also supports msxsl:script (in
its latest Beta version). In the upcoming beta release it will also support
script debugging.
You are correct, in general Stylus Studio is behaving as XSLT 1.1 about
result tree fragments handled as node-sets.
In general, the only extensions we support are:
- MSXML extensions
- Custom Java extension functions (in a way similar to what Xalan-J does)
- eXcelon XIS extensions