--- Dale Newfield <[EMAIL PROTECTED]> wrote:
> So it is clearly indicated that "redirectAction" is
> recommended over "redirect", but I neither
> understand why, nor quite what it is that this
> result type does...
Precisely for the reasons stated; it adds a layer of
abstraction that understands action configuration.
Rather than specifying an actual URL with the
namespace, action name, and action suffix you just
give it an action name (and namespace param if
necessary).
It looks up the action in the config.
It's not like it's *hugely* better than redirect, it's
just that it keeps things in the framework.
> instead be:
>
> <result name="success" type="redirectAction">
> <param name="actionName">mySuccess</param>
> <param name="fooId">${fooId}</param>
> <param name="barId">${barId}</param>
> </result>
Arguably, yes, and for a couple of reasons. Off the
top of my head I don't recall what will happen if the
param isn't found, though (or is null, etc.)
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
