Ahh, now I know. I just need to make FormSubmittingCheckBox implements
IFormSubmittingComponent and then checkBox.add(new
AjaxFormSubmitBehavior("onchange")).

Yippee!

**
Martin

2009/2/13 Timo Rantalaiho <timo.rantala...@ri.fi>:
> On Fri, 13 Feb 2009, Martin Makundi wrote:
>> Yes, this is what I am trying to do, but disabling and enabling a
>> textfield ends up clearing its value too if I use
>> AjaxFormSumitBehavior. Don't know why.
>
> Maybe a conversion error that prohibits updating the model?
> Though in the case of validation or conversion errors the
> erroneous input could be preserved... but maybe the Ajax
> update gets it from the model anyway?
>
> 0) raw input
> 1) convert -> if succeeds, convertedInput
> 2) validate -> if succeeds, model
>
> Do you have a feedback panel on the page?
>
> By debugging Form.process() you can probably see easily
> what's going on.
>
>> I feel it is more consistent to use just plain Wicket.
>
> In a way, yes, but sometimes purely client-side stuff can be
> easier purely on the client-side.
>
> Best wishes,
> Timo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to