RE: [xsl] How to output <xsl:message> to a log file

Subject: RE: [xsl] How to output <xsl:message> to a log file
From: "Mathieu Sagot" <mathieu.sagot@xxxxxxxxxxxxxxx>
Date: Fri, 17 Jun 2005 17:32:08 +0100
Thanks Dan.

I am still confused on what is exactly the standart output (or error
output) ?
I guess if I was using the XSL processor of a webbrowser, the message
would be displayed on the screen am I right ?

But because of calling the transform thru classi asp (MSXML2) is there
any way of even seeing this error output ?

Thank you

Mathieu Sagot

-----Original Message-----
From: Dan [mailto:dan@xxxxxxxxxxxxxxxx]
Sent: 17 June 2005 16:13
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] How to output <xsl:message> to a log file

> I am trying to build some error handling wich would flag the errors
> but would still carry on doing the transformation.
> I was reading that <xsl:message terminate="no"> could output the
> message to a log file, or store it in the message buffer.

<xsl:message terminate="no"> is certainly a good way to output error
messages without stopping the transformation.

<xsl:message> simply goes to standard out (or standard error); I don't
know if there's a way to redirect error messages using MSXML2. But
Michael Kay's book has a warning that you might find interesting:

"Microsoft's MSXML3 parser currently ignores <xsl:message
terminate="no"> so the message is not reported anywhere. If
terminate="yes", it generates an error, which can be handled through the
script on the HTML page that invoked the transformation."

  It's not surprising that the real world doesn't always conform
  itself to our words. What's surprising is the number of people
  who proclaim that reality is wrong "by definition".

Current Thread