Ilya A. Kriveshko wrote:
SAXESS - Hussayn Dabbous wrote:
But you also could do it directly within the xslt context:
You can use the document() function in your XSLT-file.
There are drawbacks. One of them is that Cocoon currently
(2.0.3) does not check XML sources referenced via document()
for changes. You'll get the cached result even if document()
sources change until you invalidate the main input source
for the transformation step (or the style sheet).
Q: It was said 2.1 will fix this. Is this still true?
In the past I have encountered a nasty performance problem with document().
This is a Xalan peculiarity. It acesses the source every time
a document() call is encountered, even though the XSLT spec
requires that always the same XML tree is returned (and Xalan
adheres to it). There is a bug pending (#2425).
Saxon does not have this problem. I don't know about XSLTC.
Has someone already tried?
I say,
document() is good for rapid prototyping, but is a poor choice for final
deployment for performance reasons. Use aggregation instead.
The Cocoon developers recommend to use aggregation or xinclude
because of SoC (XSLT is for transforming, not for aggregating
content). I'd add the cache issue. The performance problem
is easily dealt with.
J.Pietschmann
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
