Timo Rantalaiho wrote:
>
> What's the point of this method?
>
> And why is it calling modelChanging and modelChanged? I think
> that normally you don't call them themselves, just override
> them to react when the framework calls them.
>
> Best wishes,
> Timo
>
Well, I use this method to edit a record. The form is bound with the field
"formTarget". When called, it loads data in formTarget from the parameter.
If I don't call modelChanging/modelChanged, some components like
DropDownChoices aren't properly inited, and they select old cached values. I
don't know if it is a bug or if I wrote something wrong...
--
View this message in context:
http://www.nabble.com/Strange-behavior-with-DropDownChoice-and-PropertyModel-tf4778358.html#a13722626
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
