Stylus Studio and oXygen both include interactive debuggers that work with
Saxon.
Alternatively you can simply use xsl:message or the trace() function.
(Sometimes rather than xsl:message I use xsl:comment, which inserts the
diagnostic output into the result document).
Declaring types on all your variables and parameters is a good idea, because
it often means you get much earlier error messages. Even better is to use
schema-aware processing which will often detect your errors at compile time:
see http://www.stylusstudio.com/schema_aware.html
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Shailesh Shinde [mailto:shailesh(_at_)quagnito(_dot_)com]
Sent: 16 June 2006 08:16
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] Debugging XSL using Saxon
Hi All,
Can you please tell me how to debug xsl using Saxon.
Please provide any references for the same.
Thanks,
Shailesh
--~------------------------------------------------------------------
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>
--~--