You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Cserveny Tamas <cs...@gmail.com> on 2012/03/01 18:55:27 UTC
AjaxFormSubmitBehaviour
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 issued,
so the form errors could be displayed.
In my application it is not appropriate because the radio box changes
parts of the screen, and the user does not yet have to have a
correctly filled form.
How can I suppress this behaviour? How is it possible to use the above
behaviour in a manner that it binds all valid values and ignore
invalid ones.
In 1.4.6 it was the case.
Thank you for the answers in advance,
Cheers,
Tamas
--
Cserveny, Tamas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AjaxFormSubmitBehaviour
Posted by Cserveny Tamas <cs...@gmail.com>.
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, Mar 1, 2012 at 10:34 PM, Andrea Del Bene <an...@gmail.com> wrote:
> 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() on your form.
>
>> Hi,
>>
>> As far as I know it cannot be user with Radio components.
>> Also if I change the radio values one part of the form will be hidden.
>> If I turn it back I'll need to show the values entered already.
>>
>> Cheers,
>>
>> Tamas
>> --
>> Cserveny, Tamas
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AjaxFormSubmitBehaviour
Posted by Andrea Del Bene <an...@gmail.com>.
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() on your form.
> Hi,
>
> As far as I know it cannot be user with Radio components.
> Also if I change the radio values one part of the form will be hidden.
> If I turn it back I'll need to show the values entered already.
>
> Cheers,
>
> Tamas
> --
> Cserveny, Tamas
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AjaxFormSubmitBehaviour
Posted by Cserveny Tamas <cs...@gmail.com>.
Hi,
As far as I know it cannot be user with Radio components.
Also if I change the radio values one part of the form will be hidden.
If I turn it back I'll need to show the values entered already.
Cheers,
Tamas
--
Cserveny, Tamas
On Thu, Mar 1, 2012 at 9:56 PM, Andrea Del Bene <an...@gmail.com> wrote:
> 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 was the following:
>>
>> In case the form validationg yield errors a screenrefresh is issued,
>> so the form errors could be displayed.
>> In my application it is not appropriate because the radio box changes
>> parts of the screen, and the user does not yet have to have a
>> correctly filled form.
>>
>> How can I suppress this behaviour? How is it possible to use the above
>> behaviour in a manner that it binds all valid values and ignore
>> invalid ones.
>> In 1.4.6 it was the case.
>>
>> Thank you for the answers in advance,
>>
>> Cheers,
>>
>> Tamas
>>
>> --
>> Cserveny, Tamas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AjaxFormSubmitBehaviour
Posted by Andrea Del Bene <an...@gmail.com>.
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 was the following:
>
> In case the form validationg yield errors a screenrefresh is issued,
> so the form errors could be displayed.
> In my application it is not appropriate because the radio box changes
> parts of the screen, and the user does not yet have to have a
> correctly filled form.
>
> How can I suppress this behaviour? How is it possible to use the above
> behaviour in a manner that it binds all valid values and ignore
> invalid ones.
> In 1.4.6 it was the case.
>
> Thank you for the answers in advance,
>
> Cheers,
>
> Tamas
>
> --
> Cserveny, Tamas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org