DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33231>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33231 Summary: Wrong caching key for event pipeline Product: Cocoon 2 Version: 2.1.6 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: core AssignedTo: dev@cocoon.apache.org ReportedBy: [EMAIL PROTECTED] Use Case: A cocoon-form (main-form) for changing user preferences has a ChangePassword button which will start a new cocoon-form (sub-form) within the same continuation. In case this sub-form uses a FileGenerator and a FormsTemplateTransformer a previously cached sub-form is shown instead of the newly created one! Simplified SiteMap scenario: The main sitemap uses an aggregation for assemblying all the parts of a page. The content of the page (sub-form) is delegated to a "content.xmap". This sitemap uses a FileGenerator and the FormsTemplateTransformer which are both enclosed within a "resource-exist". If we change this FileGenerator by a none-caching JxTemplateGenerator (which doesn't make any sense because no Jx processing is needed) the problem doesn't seem to occur. Debugging and logging shows us that the sitemap request for the sub-form (in case the FileGenerator is used) wrongly uses a previoulsy cached pipe. We think the AbstractCachingProcessingPipeline causes the problem. If we would know some backgrounds about how a caching key is determined for an event pipe it could help us in isolating the problem. We would appreciate it if anyone could give us any hints or tips for tracking down this issue or much better if someone could solve it :-) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
