Hello,
I just set the exMsxsl.exe tool as an external processor in the XMLSpy but it
still
fails to support the extended functions, everything works fine when I use the
command-
line utility directly, but I would like to trace through the stylesheet for
debugging.
Is there any chance that when I try to debug the stylesheet in the XMLSPY it
gets the
default processor instead of the external I just set?
tia,
Lizet
Mensaje citado por Dimitre Novatchev <dnovatchev(_at_)yahoo(_dot_)com>:
"Américo Albuquerque" <melinor(_at_)sapo(_dot_)pt> wrote in message
news:001e01c371a3$06588ba0$bfbc37d4(_at_)lanowar(_dot_)(_dot_)(_dot_)
Hi
I think that xmlspy uses msxml that doesn't support exslt.
EXSLT support for MSXML4 (common:node-set() and all functions from the
"Sets" module) can be downloaded at http://sourceforge.net/projects/fxsl/
One can configure the command-line options of XML-SPY to work with
exMsxsl.exe (the modified msxsl.exe command-line utility, which supports
EXSLT) like this (this info provided by Oleg Tkachenko):
Tools --> Options --> XSL
External XSL transformation program:
C:\Program Files\EXSLT for MSXML4\msEXSLT\exMsxsl.exe
%1 %3 -o %2 -u '4.0*ex'
This can be used to perform transformations with XMLSPY. AFAIK XMLSPY have
their own XSLT processor used for debugging. This means that EXSLT support
will be unavailable during debugging with XMLSPY.
=====
Cheers,
Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
-------------------------------------------------
Este mensaje fue enviado usando el servicio de correo en web de Infomed
http://webmail.sld.cu
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list