I have it on reasonably good authority (somebody at a high level at Altova)
that the internal XSL engine used in XML Spy 5.* for debugging is a variant
of Saxon, not of MSXML. I haven't done any experiments to prove this to
myself, but many of the behaviors I have seen (e.g., white space handling)
are rather like Saxon's behaviors and not MSXML's.
Hope this helps,
> -----Original Message-----
> From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
> [mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com]On Behalf Of
> Sent: Tuesday, February 11, 2003 7:39 AM
> To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
> Subject: [xsl] Debugging XSL with XML Spy 5
> Does anybody know anything about the internal xsl processor that
> ships with
> XML Spy 5 ?
> This is the processor that Spy uses when with its debugging tool.
> The problem I have is that my transforms use an extension
> function - namely
> msxml's node-set function. Does anybody know if there is an equivalent in
> Spy's processor and if so what the namespace is.
Jim Melton --- Editor of ISO/IEC 9075-* (SQL) Phone: +1.801.942.0144
Oracle Corporation Oracle Email:
1930 Viscounti Drive Standards email:
Sandy, UT 84093-1063 Personal email:
USA Fax : +1.801.942.3345
= Facts are facts. However, any opinions expressed are the opinions =
= only of myself and may or may not reflect the opinions of anybody =
= else with whom I may or may not have discussed the issues at hand. =
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list