Subject: RE: [xsl] no output files From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Mon, 17 Nov 2008 13:56:59 -0000 |
There will always be at least one result tree, but its contents may be empty. see 2.4: <quote> An implicit result tree is also created when the result sequence is empty, provided that no xsl:result-document instruction has been evaluated during the course of the transformation. In this situation the implicit result tree will consist of a document node with no children. </quote> But you don't have to serialize the result tree to a file. Try <xsl:output method="saxon:net.sf.saxon.event.Sink"/> Running a transformation for the sake of its side-effects is a risky strategy - there's always a danger that the processor might optimize the whole thing away. However, it's perfectly reasonable for example for a stylesheet to be primarily performing data validation, and to produce as output a list of validation errors which may in some (or most) cases be empty. Michael Kay http://www.saxonica.com/ > -----Original Message----- > From: Szabo, Patrick (LNG-VIE) [mailto:patrick.szabo@xxxxxxxxxxxxx] > Sent: 17 November 2008 13:45 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] no output files > > Hi, > > I4m using XSLT 2.0 and Saxon 9. > Is it possible to do a transformation without creating outputfiles ?! > Why ?! > Well, the xsl doesn4t really change the files, it just uses > it4s information. > > cheers > > > Patrick Szabo > EPD / XSLT Konvertierung > Tel.: +43-1-534 52-1573 > Fax.: +43-1-534 52-1573 > patrick.szabo@xxxxxxxxxxxxx > > LexisNexis Verlag ARD Orac GmbH & Co KG > Marxergasse 25, 1030 Wien > FN 8333f, Handelsgericht Wien
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] no output files, Colin Adams | Thread | AW: [xsl] no output files, Szabo, Patrick (LNG- |
Re: [xsl] no output files, Colin Adams | Date | AW: [xsl] no output files, Szabo, Patrick (LNG- |
Month |