Using a debugger with its proprietary and also "hidden" XSLT processor
is definitely not a good idea:

1. There's no proof and no way to prove that the "internal" XSLT
processor is 100% XSLT compliant.

2. Even if the XSLT application behaves well when run with that
"internal processor" there is no guarantee that it will run in the same
way with a concrete real-world XSLT processor.


I am happy to use a great XSLT IDE that as of now provides two
debuggers -- for MSXML4 and MSXML3.


=====
Cheers,

Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL

 

"dave beattie" <dave.beattie@xxxxxxxxxxx> wrote in message
news:EB6CBF33DCE4354E8951B66EADC434EB045691@xxxxxxxxxxxxxxxxxxxxxxxx
> 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.
> 
> Thanks
> 
> Dave
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list