Isn't this correct?
onInitialize() {
super.onInitialize();
... // whatever I put here would be the same as overriding
onAfterInitialize();
}
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:35 PM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote:
> On Thu, Aug 11, 2011 at 4:35 AM, armandoxxx <armando....@dropchop.com>
> wrote:
> > Igor: thank you for your reply and your solution. Could you please
> discuss
> > this case with other developers and let me know what they think?
>
> this is the place where the developers discuss things. if any of them
> want to chime in they are free to do so. this list is our main means
> of communication.
>
> > In my
> > opinion framework should make my job easier not force me to do
> workarounds
> > to get what I need. Just a thought.
>
> nothing i have shown you is a workaround, it is using extension points
> offered by the framework to layer in new functionality specific to
> your usecase.
>
> -igor
>
>
> >
> > Martin: thank you :D
> >
> > Kind regards
> >
> > Armando
> >
> > --
> > View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Question-or-feature-request-afterOnInitialize-tp3732520p3735601.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
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
