Re: [VOTE] WICKET-3218 - Component#onInitialize is broken for Pages

[Maarten Billemont]

Perhaps one question:

Why is onInitialize invoked immediately after a component is added to a page?  
Page#componentAdded(final Component component) (line 1603 in 1.4.15).  Is it 
really necessary to initialize the page here, and if so, why?  The only 
possibly useful thing I can see it doing is 
fireComponentInitializationListeners, but why can't that just happen later, 
before the first render?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org