we also extended the Form component.... :) i think "flash" is the correct persistence strategy for Form errors. i don't see any use case where form validation messages should be stored in the session. i think it is a behaviour that is not expected.
we already had 2 developers in our company that - independently of each other - got stock with this. they had a detail page with some validation errors and chose to go back to the master page. there they selected a new article and set the new object in the detail page (via page injection or via context parameter and setupRender). and both where surprised not to see the values of the new object but the old one with the validation errors. if more people agree with "flash" as default strategy for the ValidationTracker we could add a jira :)... g, kris Nick Westgate <[EMAIL PROTECTED]> 16.10.2007 05:04 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An Tapestry users <users@tapestry.apache.org> Kopie Thema Re: T5: refreshing page when there is an error I agree it should be "Flash". I copied Form and changed it to that. It should be possible for a user to configure this. Cheers, Nick. Thiago H de Paula Figueiredo wrote: > On Mon, 15 Oct 2007 15:36:26 -0300, Howard Lewis Ship <[EMAIL PROTECTED]> > wrote: > >> Form has a clearErrors() method. > > This raises again the question on which is the best persistence strategy > for the ValidationTracker of Form: session or flash. I prefer flash, as > it makes more sense to me. On the other hand, I think Howard disagrees. :) > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
