On 10 Mar 2011, at 00:42, Igor Vaynberg wrote: > i am +0 for refactoring the code so that oninitialize() cascade is not > started from page#add() but from somewhere before page#onconfigure(). > this way oninitialize() is safe to override in pages because it will > not be invoked from page's constructor but from some framework code at > a later time.
Then I think that's the only actual solution that has positive votes. Without any further feedback, can we agree to leave constructors as they are, make onInitialize overridable and do it this way? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
