[ http://issues.apache.org/jira/browse/COCOON-608?page=all ]
Helma van der Linden closed COCOON-608:
---------------------------------------
Resolution: Fixed
> Incorrect caching behaviour
> ---------------------------
>
> Key: COCOON-608
> URL: http://issues.apache.org/jira/browse/COCOON-608
> Project: Cocoon
> Type: Bug
> Components: * Cocoon Core
> Versions: 2.1.8-dev (Current SVN)
> Environment: Operating System: other
> Platform: All
> Reporter: Alex Romayev
> Assignee: Cocoon Developers Team
> Priority: Blocker
> Attachments: test.zip
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
