cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helma van der Linden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-1137) global redirects do not work inside aggregations
Date Tue, 25 Oct 2005 14:07:00 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1137?page=all ]
     
Helma van der Linden closed COCOON-1137:
----------------------------------------

    Resolution: Fixed

> global redirects do not work inside aggregations
> ------------------------------------------------
>
>          Key: COCOON-1137
>          URL: http://issues.apache.org/jira/browse/COCOON-1137
>      Project: Cocoon
>         Type: Bug
>   Components: - Components: Sitemap
>     Versions: 2.1.4
>  Environment: Operating System: All
> Platform: PC
>     Reporter: Thomas Bierhance
>     Assignee: Cocoon Developers Team
>  Attachments: sitemap.xmap
>
> 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:/".

-- 
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


Mime
View raw message