Isn't this purely a fault with the stylesheet, rather than being
specific to saxon.net?
The reported problem was that the compile-time error messages were not being
displayed: so yes, the stylesheet is known to have errors; the problem is
with the display of diagnostics.
Michael Kay
http://www.saxonica.com/
Look at the stylesheet:
1 <?xml version="1.0" encoding="utf-8"?>
2 <xsl:stylesheet version="2.0"
3 x mlns:xsl="http://www.w3.org/1999/XSL/Transform";>
4
5 <xsl:variable name="namelist"
select="distinct-values(//*/node-name())"/>
6
7 <xsl:variable name="root" select="/"/>
8
9 <xsl:template match="/">
10 <xsl:for-each select="$namelist">
11 <xsl:variable name="thisname" select="name()"/>
12 <name value="{$thisname}"
count="{count($root//*[name() = $thisname])}"/>
13 </xsl:for-each>
14 </xsl:template>
15
16 </xsl:stylesheet>
Here $namelist contains a list of items of xdt:anyAtomicType yet it's
trying to be used as a list of nodes (when name() is called on each
item in the sequence). Saxon is probably staticly aware of this which
is why its not compiling the stylesheet, whereas other processors wont
reveal the error until runtime....
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--