I think Peter's email that started this thread was not saying that only document() should be used, but rather asking, why exclude document()?
There's a big difference between 'excluding', and 'not recommending for specific usecases'. AFAIK, nobody 'excluded' the use of document() in Cocoon. I think some are just trying to warn people that one should be aware of the side-effects caused by the use of this function.
Whether one likes it or not, we have seen huge performance gains by minimizing the number of XSLT transformations in a pipeline, even at the end of building one-off custom SAXTransformers to replace some XSLT stylesheets. Cocoon is XML-centric, and might be a nice environment to do server-side XSLT transformations, but I find it difficult to state that XSLT (and the document() function) is the panacea for all webapp development related problems, or more specific aggregation, or whatelse.
That being said, if anything is missing w.r.t. document() / Source / caching support in Cocoon (or Xalan!), I'm pretty sure patches will be accepted gratefully.
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
