Cool - thanks Seb - I'll look into it...! :)
-Original Message-
From: Sebastien [mailto:seb...@gmail.com]
Sent: Thursday, 1 October 2015 6:13 PM
To: Patrick Davids <patrick.dav...@nubologic.com>
Cc: users@wicket.apache.org
Subject: Re: Components/Behaviour execution order
Hi,
@P
Hi,
@Patrick
Yes, we had a behavior sequence order issue [1] that we just solved by
calling super.onConfigure(component); at the end of #onConfigure.
@Colin
When I've complex cases, I am using the event bus. The key point is my
magic AjaxPayload base class, so you can create
Hi Col.,
sometimes I try to cheat by using onBeforeRender() in such cases to
'fake' an order, because its called after onConfigure().
But this has some restrictions concerning visibility issues of components.
But in simple dependencies this sometimes works for me.
I think somewhere in wickets
