DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4641>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4641 Design of Source interface precludes implementation of CachingCIncludeTransformer [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Status|CLOSED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-06-16 12:05 ------- I am still seeing this bug in 2.0.5-dev (using a CVS checkout that is a few weeks old, but I don't think anything relevant has changed recently). If a CachingCIncludeTransformer is used in one pipeline, and another pipeline then pulls from this using the 'cocoon:' protocol, the cached content for the first pipeline will be not be invalidated if one of the documents included by the CachingCIncludeTransformer changes. As described in the original bug report, this is because: 1) SitemapSource uses a hash of the String representation of the validity objects for the relevant pipeline. 2) The IncludeCacheValidity object does not contain any information until the CachingCIncludeTransformer has received it's SAX events, so its String representation is always the same before then. This problem does NOT occur if the CachingCIncludeTransformer is in the final pipeline. I have a workaround patch for this problem that provides the correct behaviour, but it is neither pretty nor well tested. I can put together a test case if required.
