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=28650>. 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=28650 global redirects do not work inside aggregations Summary: global redirects do not work inside aggregations Product: Cocoon 2 Version: 2.1.4 Platform: PC OS/Version: All Status: NEW Severity: Normal Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The documentation says that the option global="true" or global="yes" should make it possible to abort an aggregation and send a redirect via http. http://cocoon.apache.org/2.1/userdocs/concepts/redirection.html#Global+Redirects That does not work using Cocoon 2.1.4. Excerpt from a sitemap: <map:pipeline> <map:match pattern="redirect"> <map:redirect-to uri="redirected"/> </map:match> <map:match pattern="aggregate"> <map:aggregate element="root"> <map:part src="cocoon://aggregatedRedirect"/> </map:aggregate> <map:serialize/> </map:match> <map:match pattern="aggregatedRedirect"> <map:redirect-to global="true" uri="redirected"/> </map:match> </map:pipeline> Accessing "redirect" correctly results in a http-redirect to "redirected". However, "aggregate" is trying to resolve "redirected" internally and does not send the redirect. I had a look on what's going on, but as sitemap processing involves quiet a lot a things, I could not figure it out exactly. I could observe however, that the attribute "global" gets lost (is not present in the node's "Configuration" object) and that the uri somehow gets prefixed with "cocoon:/".
