[ https://issues.apache.org/jira/browse/COCOON3-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279753#comment-13279753 ]
Javier Puerto commented on COCOON3-30: -------------------------------------- I've noticed while developing the patch for COCOON3-100 that ParameterCacheKey break the caching returning "-1" for last modified value. This make caching by last modified useless because it's used for all pipelines. > The current implementation of the ParameterCacheKey actually breaks the > caching > ------------------------------------------------------------------------------- > > Key: COCOON3-30 > URL: https://issues.apache.org/jira/browse/COCOON3-30 > Project: Cocoon 3 > Issue Type: Bug > Components: cocoon-pipeline > Affects Versions: 3.0.0-alpha-1 > Reporter: Steven Dolg > Assignee: Steven Dolg > Priority: Critical > Fix For: 3.0.0-alpha-2 > > Attachments: parametercachekey.patch > > > The equals() and hashcode() implementations of the ParameterCacheKey do *not* > take the actual parameters into account. > This makes it possible that different pipeline setups have the same cache key > and overwrite their cached results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira