This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: template stack trace
- To: emberson at contact dot com
- Subject: [xsl] Re: template stack trace
- From: Dimitre Novatchev <dnovatchev at yahoo dot com>
- Date: Fri, 27 Jul 2001 09:55:56 -0700 (PDT)
- Cc: xsl-list at lists dot mulberrytech dot com
- Reply-To: xsl-list at lists dot mulberrytech dot com
Richard Emberson wrote:
> One can use the <xsl:message terminate="yes> .... </message>
> as a method of indicating that a fatal error occurred in your xslt
> program.
> What I would like is to be able to print out the named-template stack
> trace
> so that I can tell the context inwhich the error arose.
>
> (if template A calls template B calls template C and in C a fatal error
> is
> detected, how do I find out that I am within templates A and B?)
Richard,
The best way to achieve this is to have a good XSLT Debugger.
With the Xselerator, I place a breakpoint at the line with the "xsl:message"
and when/if the Debugger stops at that breakpoint, I simply watch the "Call stack"
window.
Without a debugger you cannot achive this without significantly changing you code --
sometimes this can be very difficult!
Cheers,
Dimitre Novatchev.
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list