Do "real forwards" have the ability to stay within the same sitemap? I'm assuming this method would call the RequestDispatcher's forward method? If so, would this finally allow constructs such as <map:redirect-to uri="cocoon:/../parent-pipeline"> ? This would seem logical as you'd have to construct the full path to stay within the current sitemap anyway.
Ralph -----Original Message----- From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 7:21 AM To: Cocoon-Dev Subject: [Vote] Change internal redirect handling As discussed recently, our internal redirects don't work the way one would usually suspect. If you do an internal redirect, like: <map:redirect-to uri="cocoon://some-pipeline"/> and the called pipeline has an error, then the error handler of the calling pipeline (containing the redirect) is called and not the error handler of the called pipeline. So, the above line is not the same as: <map:redirect-to uri="some-pipeline"/> So, we have three choices to change this: a) Make an internal redirect a real forward (This is an incompatible change) b) Make it configurable on the uri, like <map:redirect-to uri="cocoon://some-pipeline?cocoon:forward=true"/> c) Make it configurable on the map:redirect, like <map:redirect-to uri="cocoon://some-pipeline" forward="true"/> For solutions b) and c) we can discuss the correct syntax later on, let's for now focus on the way we want to have it. Although this is an incompatible change, I prefer a) as it is imho the right way of doing the redirect. Please cast your votes for either a), b) or c) Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.osoco.net/weblogs/rael/
