On Wed, May 9, 2012 at 2:22 PM, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi Thomas,
>
> On Wed, May 9, 2012 at 2:12 PM, Thomas Heigl <tho...@umschalt.com> wrote:
>> Hello,
>>
>> I notices a strange behavior after upgrading to Wicket 1.5. Nested forms
>> are submitted in a different order.
>>
>> I have structures like this:
>>
>> - Compound Form
>>> -- Subform 1
>>> -- Subform 2
>>> -- Subform 3
>>> - Submit Link/Button for Compound Form
>>
>>
>> In Wicket 1.4 the order of calls to onSubmit was like this:
>>
>> 1. Subforms
>> 2. Compound Form
>> 3. Submit Link/Button
>>
>> In multiple locations I had logic in the subforms' onSubmit handlers that
>> do cleanup, re-attaching of models to entities etc. before my links submit
>> handler is called and persists my model object.
>>
>> In Wicket 1.5 the submit link's handler that I use for my main logic is
>> actually called before the subforms:
>>
>> 1. Submit Link
>> 2. Subforms
>> 3. Compound Form
>>
>> I can fix this by moving all my compound form logic from the link/buttons
>> onSubmit handler to the compound form's handler, but wanted to check first
>> if this behavior is intentional?
>> Is this the way to do it in Wicket 1.5?
>
> This is the way how it works in 1.5/6.x. I'm not sure why it is not 
> documented.
> But there are different opinions about it:
> https://issues.apache.org/jira/browse/WICKET-3705

WICKET-3705 links to https://issues.apache.org/jira/browse/WICKET-1894
which says that this order is changed in 1.4.15

>
>>
>> Cheers,
>>
>> Thomas
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

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

Reply via email to