RE: no output files
> The fact that in this case a file (empty) is still created > seems like a bug. It is actually a deliberate design choice, after a reasoned debate. Given that an XSLT stylesheet can be used to create an external general parsed entity, and that an external general parsed entity can legitimately be "empty", we felt that <xsl:param name="n" as="xs:integer"/> <xsl:template match="/"> <xsl:for-each select="1 to $n"> <xsl:text>baa</xsl:text> </xsl:for-each> </xsl:template> should produce an EGPE whose value contains $n repetitions of the string 'baa', in all cases including when $n=0. It's also relevant for example if the output of the stylesheet is a list of data errors found in the source document. If there are no such data errors, the next stage in the processing pipeline should expect to see an empty list. It's quite possible in this case that the result will be passed to the next stage as an XDM tree, without being serialized. Michael Kay http://www.saxonica.com/
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format