Saxon

Legacy ID: #3109107 Legacy Poster: Michael Kay (mhkay)

If you're invoking this from the command line, you need to specify the -o option to give the principal output destination. The "text.xml" will be interpreted relative to this destination. If you're running it using JAXP, make sure that the Result object supplied to the transform() method has a known system ID (by calling setSystemId() on it). Michael Kay http://www.saxonica.com/

Legacy ID: #3109529 Legacy Poster: Boris Kaminer (boris_kaminer)

Thank you.. But this is very strange, why saxon doesn't assume current working directory as the principal output destination by default as it was in previous versions? If i specified -o . then i got error that output is directory but input isn't. why does it matter?

Legacy ID: #3109993 Legacy Poster: Michael Kay (mhkay)

The main reason that there's no default for the principal output destination is security, when running stylesheets in a web server environment. However, I agree that it could be done easily enough when running from the command line, and that's been on my "to do" list for a while. If a principal output file is specified using -o it must be a file and not a directory. Specify a dummy file if necessary. Yes, I know that's not a brilliant user interface! Michael Kay

Legacy ID: #3110655 Legacy Poster: Boris Kaminer (boris_kaminer)

Thank you for explanation! What do you think about using term "principal output" in documentation article for xsl:result-document to describe purpose of -o flag?