On Tuesday, April 9, 2002, at 10:17 AM, Nicola Ken Barozzi wrote:
>
>> I'd like to propose to add a <map:forward path="" /> node to sitemap.
>> Behavior should be the same as <map:redirect-to uri="cocoon:/..." />.
>
> What's different from current map:call ?
>
> <map:call resource="dynamic-page">
> <map:parameter name="target" value="{../target}1"/>
> </map:call>
I can see value in a more explicit facility for redirecting to an
existing sitemap match as opposed to a resource. However, if this is
the case, then I presume that the passed parameters would be treated as
http request parameters and not variables in the environment map.
For reasons of accessibility there are situations when it would be
extremely valuable to output the contents of another web page in
response to request failure or other detectable condition without using
a 'real redirect' (status code 302). Real redirects are considered a
'no no' on accessible sites but producing the resulting pages as
resources instead of site matches seems clumsy and unrepresentative of
the intention of the code.
I believe that this facility is already available in the form (but I
haven't tried it!):
<map:redirect-to uri="cocoon://path?param1=value1&param2=value2" />
But as Konstantine says, this is not very intuitive and I would be +1
for:
<map:forward path="path">
<map:parameter name="param1" value="value1" />
<map:parameter name="param2" value="value2" />
</map:forward>
Stuart.
Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck (Adolos)
Key fingerprint = 89D9 E405 F8B1 9B22 0FA2 F2C1 9E57 5AB1 88DD 65AF
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Systems Architect Java, XML, MacOS X, XP,
etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
