Altova Mailing List Archives

RE: [xsl] results in zero byte file getting written

From: "Michael Kay" <mike@------------>
Date: 3/29/2007 7:13:00 PM
> I am also facing similar kind of issue ,during transfor if I 
> have xsl:message with terminate=yes and it is redirected to 
> System.err and It does not fall as Exception

In Saxon, by default, if you don't specify a MessageReceiver and don't do
anything to change the behaviour of the standard one, then <xsl:message
terminate="yes">ABANDON SHIP</xsl:message> should result in the text
"ABANDON SHIP" being written to System.err, and to an exception of class
net.sf.saxon.trans.TerminationException being thrown, with the exception

"Processing terminated by xsl:message at line NNN in URI.xsl"

If you are running from the command line, the application will terminate
with exit code 1.

If you want to capture the message text in your application, you need to
call setMessageEmitter() to supply your own code to receive xsl:message

Michael Kay


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.