On Fri, 2004-06-04 at 12:02, Joerg Heinicke wrote:
> On 03.06.2004 14:55, Peter Flynn wrote:
[caching]
> http://issues.apache.org/bugzilla/show_bug.cgi?id=10203
>
> From the bug date you will also see, that there will probably be no
> short-term fix.
That's actually the reverse of this problem: the OP seems
to be complaining that ancillary data retrieved from a call
to the document() function is *not* being cached, whereas
in fact it *is* (and shouldn't be) -- and the waters were
muddied by the problem being confused with the behaviour of
xsl:include.
Not important now: I coded around it. But it would be a big
benefit to the behaviour of Cocoon if this was fixed: it is
*not*, as Carsten suggests, a "feature request": it's a bug.
If I write
<xsl:value-of select="document('foo.xml')/bar/@blort"/>
and it emits the string "xyz" because foo.xml contains
<bar blort="xyz"/>
and then an external system changes foo.xml so that it now
contains
<bar blort="abc"/>
and I reload the URI of the pipeline in my browser, I still
get "xyz" because the content of the file was cached.
Whatever code in Cocoon that is performing this caching
simply needs to be removed.
///Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
