Thank you very much, Thomas, I was struggling with exactly this problem
for a couple of hours yesterday... I think this should be changed back
or at least be configurable in the next versions !
Cheers,
Stefan
Am 13.06.2012 17:14, schrieb Thomas Heigl:
Hello,
In case anyone else is encounteri
Hello,
In case anyone else is encountering this problem when migrating from 1.4 to
1.5, I solved it by overriding delegateSubmit in my form:
public static enum SubmitOrder {
> /** Submit form submitter before forms (1.5 Default) */
> OUTSIDE_IN,
> /** Submit form submitter after forms (1.4 Defaul
Hey Martin,
> WICKET-3705 links to https://issues.apache.org/jira/browse/WICKET-1894
> which says that this order is changed in 1.4.15
I upgraded to Wicket 1.5 from Wicket 1.4.20 and it still has been working
with 1.4.20.
This is the way how it works in 1.5/6.x. I'm not sure why it is not
> do
On Wed, May 9, 2012 at 2:22 PM, Martin Grigorov wrote:
> Hi Thomas,
>
> On Wed, May 9, 2012 at 2:12 PM, Thomas Heigl 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:
>>
>> - Co
Hi Thomas,
On Wed, May 9, 2012 at 2:12 PM, Thomas Heigl 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
>> - Subm
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 wa
