Actually, you can make it redirect, but this affects the whole
application, since you need to make change in <controller> element:
<controller inputForward="true"/> Then you will need to refer a
<forward> element in your "input" property:
<action ... input = "itemError">
...
<forward name="itemError" path="/displayError.do" redirect="true"/>
</action>
Because this involves a regular <forward> element anyway, I think that
"input" in its current state does not make much sense. We can simply
have a designated <forward> for input errors, with predefened mapping
name, like ERROR_INPUT:
<action>
...
<forward name="ERROR_INPUT" path="/displayError.do" redirect="true"/>
</action>
This will also allow to have several error handlers, with names
starting on "ERROR_" or something. Just a thought.
Michael.
On 5/11/05, Benedict, Paul C <[EMAIL PROTECTED]> wrote:
> From all this discussion, something occurred to me:
>
> I think someone should submit an enhancement for Struts 1.2.8/1.3, so that
> we can define the input page as an action forward/redirect:
>
> <action path="/test" type="com.company.someClass">
> <forward name="input" path="/letsGoHere.do" redirect="true" />
> <forward name="success" path="page.success" />
> </action>
>
> After talking with Michael, this solution would solve one of the
> input/output problems that need to be addressed: greater control over the
> error page. By having the "input" be a reserved forward, developers could
> also say it is a redirect.
>
> Can someone investigate the impact of modifying the getInputForward method?
>
> Thanks,
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
