Hi Armando, the problem #1 is rather about not have the entire component tree connected already. onInitialize is called when the component is aware of its path to page, at this moment, a triggered even will not reach new nodes addition in the component tree.
On Wed, Aug 10, 2011 at 7:23 AM, armandoxxx <armando....@dropchop.com> wrote: > Hey guys ... > > With wicket 1.5 we got events. So far so good but I got a case where i'm > missing after on initialize method call. > > I have lot's of panels on my page, and I create them in onInitialize() code. > But I need to send a 1 time event after all components are initialized. > - problem #1: If I send an event from onInitialize(): not sure that all > components are initialized ! > - problem #2: If is send an event from onConfigure() or onBeforeRender(), > the event get send everytime component is rendered ... > > So current solution is to create a flag in my panels that sendEventOnInit() > method was allready called .. > > but it would be better to have a method onInitialized() | > afterInitialized() (pick your favorite name). > > If someone has better approach, please let me know about it ! > > Kind regards > > Armando > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Question-or-feature-request-afterOnInitialize-tp3732520p3732520.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Pedro Henrique Oliveira dos Santos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
