+1 for clear documentation/Javadoc explaining proper use of onInitialize. Does this exist somewhere? As someone new to Wicket I'm trying to learn as fast as I can and a lot of examples (almost exclusively) I see out there show the add(..) from within the constructor - which is apparently an anti-pattern from the sound of this thread.
Thanks, Matt -----Original Message----- From: Hans Lesmeister 2 [mailto:hans.lesmeis...@lessy-software.de] Sent: Tuesday, March 08, 2011 11:38 AM To: users@wicket.apache.org Subject: Re: [VOTE] WICKET-3218 - Component#onInitialize is broken for Pages +1 for making Page.onInitialize() non-final. Since 1.4.12 we have migrated a lot of code moving construction of the component hierarchies to onInitialize. We are really very happy with the way it is now in 1.4. +1 for clear documentation/Javadoc explaining proper use of onInitialize. (Developers who don't want to follow that explanation do also not have to be protected agains themselves) -1 for throwing an exception if add(..) is called from within a constructor (but maybe logging a warning instead?) I would also not have a problem with an alternative onInitialize()-method for the Pages. ----- -- Regards, Hans http://cantaa.de -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/VOTE-WICKET-3218-Component-on Initialize-is-broken-for-Pages-tp3341090p3341741.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
