See this faq about using XSLT document() in Cocoon, which includes a mention of this bug: http://cocoon.apache.org/2.0/faq/faq-xslt.html#faq-6
This is the "cacheability" problem referred to:
when you execute an XSLT transform that calls the "document('foo.xml')" method, the date stamp of the file foo.xml is not included in the CacheValidity of the transform. So even after you modify foo.xml, the pipeline will continue to serve the cached results.
Cheers Con
Ah! That explains some strange behaviour I experienced.
Does it help to put the XML broking pipe in a non-caching pipeline?
Cheers, Geert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
