[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: no output files

Subject: RE: no output files
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Wed, 19 Nov 2008 15:18:52 -0000
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">

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

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.