Fabio Fioretti wrote: > > You were right Kent, thanks a lot! Calling clearInput() in the > updating behavior really fixes the problem. > > What I miss now is why the CompoundPropertyModel breaks if the form is > not manually reset by calling clearInput(). Is it a bug or a feature? > :) >
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. ----- -- Kent Tong Wicket tutorials freely available at http://www.agileskills2.org/EWDW -- View this message in context: http://www.nabble.com/CompoundPropertyModel-stops-working-when-form-validation-fails.-tf4562483.html#a13092730 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
