>> Cancelable Actions (independently on the Action type: normal Actions, >> DispatchActions) could even implement a Cancelable interface with a cancel method.
Tamas, good one. I thought of this too but never mentioned it because implementing interfaces doesn't seem too cool/accepted in the Struts framework yet. (But that will change in 1.3.) If I add a Cancelable interface to my actions, then that could indicate to the framework that these actions deserve to be canceled; otherwise ignore the request parameter. Rick, your suggestion is good too. Did you know Tapestry works the same way? You're in charge of calling the validator and determining what it should do. In your case you would always want the form populated so you could determine if to validate or not. Frank, I agree: I don't think it makes sense populating the form if validate="true" and the cancel token is in the parameter. Besides, the extra benefit here is that if you're in a form wizard and you have 2 out of 3 pages validated, if they cancel on the 3rd page, you at least have 2 pages of data that you know is good; re-populating the form without validation then looses this confidence. Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
