On 10/8/07, Kent Tong <[EMAIL PROTECTED]> wrote: > It's a feature. When the selection changes, the user might have entered > something into say a text field. Generally we don't want to lose that > input (because all you want to do may be to show or hide a certain component > depending on the selection), therefore it is saved and redisplayed to the > user. By default it is clear only when the form is submitted and validation > is passed successfully.
Ok, this behavior is understandable and fine. But when, after a failed validation, the model object of the form is changed (by a new user's selection on the ListChoice) and the form is refreshed, I'd expect it to display the newly selected instance instead of the one that failed validation. I mean, it's ok that the input isn't lost when validation fails, but this should be limited to the object that actually failed validation and it should't prevent using the form to manipulate another instance after having changed form's model object accordingly. In this sense, the feature looks like a limitation in my particular case. Of course I may be missing something, or not using the form as it is meant to be used... Thanks a lot, Fabio Fioretti - WindoM --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
