I still think it's not a bug, it's only a clarification or rectification of the behaviour of Cocoon. There is now a <map:redirect-to uri=""/> for client side redirects and a <map:call resource=""/> for internal redirects. The documentation (http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html) states this unequivocal:
1. Paragraph "Redirecting":
Redirecting forwards the the request. You may externally send an redirect response to the client. The behaviour is controlled by using the approriate attributes of the element redirect-to. ...
(I don't know why <map:redirect-to resource=""/> still works. Backward compatibility?)
2. Paragraph "Calling resources":
Calling resources is dissimilar to redirects as the client does not notice this.
3. Paragraph "Protocols":
In the sitemap, you can use all protocols nearly everywhere (except for in map:redirect).
So what's wrong with it besides that <map:redirect-to resource=""/> still works? Maybe there is a difference in behaviour between the tree processor and the old sitemap system using XSL and Java compiling (How do you call this?). Can Sylvain say something on this point (his name is in the tree processor classes)? Or does anybody else know something more?
Regards,
Joerg
Timothy Larson wrote:
Status of redirects in Cocoon-2.0.4:
Does work:
Client side redirect:
<map:redirect-to uri="sample.html"/>
Internal redirect with underscore in resource name:
<map:redirect-to resource="sample_html"/>
Does NOT work:
Internal redirect with cocoon:/ protocol (used to work in 2.0.2/2.0.3):
<map:redirect-to uri="cocoon:/sample.html"/>
Internal redirect with period in resource name (doubt it ever worked):
<map:redirect-to resource="sample.html"/>
As a side note, http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html says
"map:redirect" where it should say "map:redirect-to":
Protocols
In the sitemap, you can use all protocols nearly everywhere (except for in map:redirect).
How can I help get these fixed?
Tim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
