Tamas Szabo on 22/01/06 07:30, wrote:
There is a legitimate case: when an form can be cancelled, you do
want to skip client-side and server-side validation. That's just
fine because in these case you do want to call the cancelled()
method from DispatchAction, dump out any state you collected, and
go to the appropriate forward.
In my oppinion it isn't ahndled correctly and I don't think that it
should be solved by configuration script. If the user presses Cancel
then the processing should go on another path. It doesn't make sense
to populate and to validate if cancel was pressed.
I agree. I _do_ use the cancel button on many forms and this is what I
implement - if Struts did it itself, it would save me time and effort.
Plus it would be safer on other actions where I don't use the cancel
button.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
