> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]] 
>
> Hi team,
> 
> I implemented internal redirects using the "cocoon:" pseudo-protocol. 
> This is the Cocoon-equivalent to servlet request forwarding.
> 
> This means that writing
>   <map:match pattern="">
>     <map:redirect-to uri="cocoon:/index.html"/>
>   </map:match>
> will make a recursive call on the current processor to serve 
> "index.html" without going back to the client browser.
> 
> This is also available in the Redirector used by actions. And 
> as usual, 
> "cocoon:/xxx" uses the current sitemap, and "cocoon://xxx" 
> uses the root 
> sitemap.

Cool!
But as I remember, there were something like that already:
<map:redirect resource="/path/to/pipeline" />

Is it different from your version?

> 
> This feature will be especially usefull with the flow engine, 
> since the 
> flow script chooses the page that comes next and should be 
> able to call 
> this page without losing business data that may be stored as request 
> attributes.

Just yesterday was thinking of that. Struts uses exactly that for flow
processing, thus you can chain actions and select the  flow of processing
based on the returned result from every action.

> 
> This is implemented in 
> org.apache.cocoon.environment.ForwardRedirector 
> and used for now only by the treeprocessor (so I didn't update the 
> samples to avoid to break them). Integration with the compiled engine 
> should be fairly easy, but I'm sooo late on my paid work, so 
> any takers 
> are welcome.

Btw, do we still need to support compiled version if we switch to
TreeProcessor?

Regards,
Konstantin

> 
> Enjoy,
> Sylvain
> 
> -- 
> Sylvain Wallez
>   Anyware Technologies                  Apache Cocoon
>   http://www.anyware-tech.com           mailto:[EMAIL PROTECTED]
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to