Hi,
I tried to override the whole onEvent() part and use processInput() on
some of the fields. Even if I cleared the messages or whatever, the
refresh was made right after the response.
I'll check the setDefaultProcess(), maybe it will help.
Thanks,
Cheers.
Tamas
--
Cserveny, Tamas
On Thu,
yes, for radio choice you should use
AjaxFormChoiceComponentUpdatingBehavior. Anyway, have you tried setting
default form processing to false on AjaxFormSubmitBehavior
(setDefaultProcessing(false))? In this way you could save fields' value
inside onSubmit() calling updateFormComponentModels()
> Hi,
> isn't AjaxFormComponentUpdatingBehavior more suited for your need?
>>
>> Hi,
>>
>> I''ve upgraded my wicket application from 1.4.6 to 1.4.19. I was using
>> AjaxFormSubmitBehaviour
>> mainly because I need to respond to a change in a
Hi,
isn't AjaxFormComponentUpdatingBehavior more suited for your need?
Hi,
I''ve upgraded my wicket application from 1.4.6 to 1.4.19. I was using
AjaxFormSubmitBehaviour
mainly because I need to respond to a change in a radiobox. One main
difference was between the versions wa
Hi,
I''ve upgraded my wicket application from 1.4.6 to 1.4.19. I was using
AjaxFormSubmitBehaviour
mainly because I need to respond to a change in a radiobox. One main
difference was between the versions was the following:
In case the form validationg yield errors a screenrefresh is