RE: [xsl] writing error file

["Michael Kay" <mike@xxxxxxxxxxxx>]

I can't reproduce your problem. Given c:\temp\test.xsl:

<?xml version="1.0" encoding="UTF-8"?> 
<xsl:stylesheet 
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; 
    version="2.0"> 
    <xsl:template match="/"> 
        <a>
        <xsl:message>A message</xsl:message>
        </a> 
    </xsl:template>
</xsl:stylesheet>

running

cd c:\temp
java net.sf.saxon.Transform test.xsl test.xsl 2>test.log

creates file c:\temp\test.log containing:

A message

I also tried 2>>test.log (something I hadn't seen before): this appended the
message to the previous contents of the file rather than overwriting it.

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: Frank Marent [mailto:frank.marent@xxxxxxxxxxx] 
> Sent: 22 September 2006 07:00
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] writing error file
> 
> michael
> 
> > "2>error.log" should work. If not, it's really an operating system 
> > question rather than a Saxon or XSLT problem, but I guess 
> we can help 
> > if you tell us exactly what OS environment you are in and 
> what command 
> > shell you are using.
> 
> we're working under windows xp. and we're calling a normal 
> .bat file to start transformation:
> 
> [process.bat]
> > set errorfilename=C:\errors\%date:~-4%%date:~-7,2%%date:~-10,2%.log
> > set saxdir=C:\Programme\saxonb8
> > set filedir=C:\XMLBatchProcessor\input
> > java -jar %saxdir%\saxon8.jar -o %3 %3 first.xsl >> 
> %errorfilename% ..
> > .. (calling further xslts)
> > ..
> > ..
> 
> 
> - %3 represents full path and filename of the xml file to be 
> transformed
> - 'errorfilename' will be used as '20060921.log'
> - '2>> % errorfilename%' was writing saxon error messages, but did
> *not* write xsl:message messages
> - '>> % errorfilename%' produces no output
> - we're not able to implement a MessageEmitter and only 
> working on .bat level
> 
> 
> appreciating your help,
> hoping my information is enough detailled
> 
> frank