onInitialize or Constructor

[Josh Kamau]

Hi wicketeers ;

Which is the recommended way of initializing page components: onInitialize()
or Constructor ?

regards.
Josh.

Re: onInitialize or Constructor

[Martin Grigorov]

Use onInitialize() if you need access to the parent component or to
the associated markup

On Wed, Oct 19, 2011 at 3:28 PM, Josh Kamau joshnet2...@gmail.com wrote:
 Hi wicketeers ;

 Which is the recommended way of initializing page components: onInitialize()
 or Constructor ?

 regards.
 Josh.




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: onInitialize or Constructor

[Andrea Del Bene]

Hi,

when onInitialize is called, component has already been inserted into 
its hierarchy so you can call getParent() or getPage() safely.

Hi wicketeers ;

Which is the recommended way of initializing page components: onInitialize()
or Constructor ?

regards.
Josh.




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: onInitialize or Constructor

[Josh Kamau]

Thanks. Its clear now.

On Wed, Oct 19, 2011 at 4:01 PM, Andrea Del Bene adelb...@ciseonweb.itwrote:

 Hi,

 when onInitialize is called, component has already been inserted into its
 hierarchy so you can call getParent() or getPage() safely.

  Hi wicketeers ;

 Which is the recommended way of initializing page components:
 onInitialize()
 or Constructor ?

 regards.
 Josh.



 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org