I wrote this er... piece originally. You are right, the problen and solution are explained badly. The original point was that "input" property is a sucky one and should not be used at all. One of the reasons was that it could not redirect. But turned out that it actually can redirect, so I added the whole paragraph of how to redirect to "input". But this really does not help because error messages are gone.
So, I personally _never_ use evil "input" property. Instead, I call validate() manually from an action class, and manually save errors. If you want to save errors from an action form, you can save reference to session in reset() method, and then use it in validate(). The problem is that reset() is not called for request-scoped forms (I think so, I do not remember now clearly...). So, you stuck. Therefore, the recommendation should be: if you want to redirect on error, * do not use "input" property * do not use automatic validation Call validate() manually from action class and save errors to session manually. Starting from 1.2.6 these errors are removed automatically after they accessed. I will change the wording in this entry, thanks for pointing out. Michael. P.S. "Next" means 1.3 if I am not mistaken. The code is there, in SVN. On 7/15/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > I just read the StrutsCatalogRedirectToInputPage wiki entry [1] and have a > question: given that failed validation causes the action not to be called, > where exactly am I supposed to call Action.saveMessages()? Is this even > required? Shouldn't it be handled by the validator already? > > L. > > PS, the entry closes with a note referencing the 'next Struts version'; > next after what? > > http://wiki.apache.org/struts/StrutsCatalogRedirectToInputPage > -- > Laurie, Open Source advocate, Java geek and novice blogger: > http://www.holoweb.net/~laurie/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
