View Single Post
  #2 (permalink)  
Old December 15th, 2008, 09:48 AM
mhkay's Avatar
mhkay mhkay is offline
Wrox Author
Points: 18,487, Level: 59
Points: 18,487, Level: 59 Points: 18,487, Level: 59 Points: 18,487, Level: 59
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Apr 2004
Location: Reading, Berks, United Kingdom.
Posts: 4,962
Thanks: 0
Thanked 292 Times in 287 Posts

First, an aside: using a DOMSource with Saxon is really inefficient and you should only do it if you already have the source in the form of a DOM. Much better to let Saxon build the tree in its own native format.

Second point: you're asking a question here that's very specific to Saxon. The best place to do that is on the saxon-help mailing list or forum which you can reach via the saxon project on sourceforge. The advantage of doing that is that users can help each other much better if they all meet in the same place.

In theory the output files should be written to the same directory as the principal output. I'll try to run a test similar to your code to see if I can reproduce the problem.

You should be able to see where the files are being written by using

processor.setProperty(FeatureKeys.TIMING, "true")

This is equivalent to the -t option on the command line.
Michael Kay
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference
Reply With Quote
The Following User Says Thank You to mhkay For This Useful Post:
maikm (December 15th, 2008)