I would think the problem has nothing to do with validation. There are quite a number of things that can cause a tree to be built in memory when you wanted streamed processing; for example, the configuration might not be an EnterpriseConfiguration, or it might be that no license file was found. Start by ensuring that the -t option is on (assuming you are running from the command line: otherwise, FeatureKeys.TIMING). Then tell us exactly how you are running the transformation, and show all the messages.

Michael Kay

On 12/03/2012 14:12, Todd Gochenour wrote:
And now I'm getting Java Heap Space errors with the large file.   It's as if the doc() function inside the stream() function is validating the document and this is what is consuming the heap.  The debugger steps through the stream() function to the doc() function, pauses, and then throws the heap exception.    Can I turn off validation so I can process a 704Meg file?

Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!

saxon-help mailing list archived at http://saxon.markmail.org/