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=17623>. 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=17623 Incorrect caching behaviour Summary: Incorrect caching behaviour Product: Cocoon 2 Version: Current CVS Platform: All OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It appears when a generator uses an output of another match (say a.resource), when a.resourse changes, the cache of the pipeline that uses its output does not get invalidated. Here is an example of the sitemap that exibits this behaviour: <map:components> <map:actions> <map:action name="request" src="org.apache.cocoon.acting.RequestParamAction"/> </map:actions> </map:components> <map:pipelines> <map:pipeline> <map:match pattern="*.portlet"> <map:match pattern="a.portlet"> <map:generate src="cocoon:/a.resource"/> <map:serialize type="xml"/> </map:match> </map:match> <map:match pattern="*.resource"> <map:match pattern="a.resource"> <map:act type="request"> <map:parameter name="parameters" value="true"/> <map:generate src="{locale}.xml"/> <map:serialize type="xml"/> </map:act> </map:match> </map:match> </map:pipeline> </map:pipelines>