This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: template stack trace
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] template stack trace
- From: "Ivan Pedruzzi" <ivan at exceloncorp dot com>
- Date: Fri, 27 Jul 2001 16:34:26 -0400
- Reply-To: xsl-list at lists dot mulberrytech dot com
You should try to use an XSL debugger.
Ivan Pedruzzi
eXcelon Corporation
http://www.stylusstudio.com
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of
> Richard Emberson
> Sent: Friday, July 27, 2001 1:32 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] template stack trace
>
>
>
> 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?)
>
> Thanks
>
> RME
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list