Hi,
I'm not sure whether there is a specific reason why this method is not in
the API.
Maybe just because no one needed/noticed it.
Maybe there is something wrong in it which I don't see at the moment.
Anyway create a ticket for improvement.
Yet another way is to use
What happens if the behavior is added after the component has already been
initialized? Does its oninitialize() still get called? Ambiguities like
this is the reason why there is no such method.
-igor
On Wednesday, February 6, 2013, Colin Rogers wrote:
Martin and other Wicketeers,
I have a
To: users@wicket.apache.org
Subject: Re: Behaviour.onInitialise()
What happens if the behavior is added after the component has already been
initialized? Does its oninitialize() still get called? Ambiguities like this is
the reason why there is no such method.
-igor
On Wednesday, February 6
may be able to better help you.
-igor
Cheers,
Col.
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: 07 February 2013 19:14
To: users@wicket.apache.org
Subject: Re: Behaviour.onInitialise()
What happens if the behavior is added after the component
! :)
Cheers,
Col.
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: 08 February 2013 10:59
To: users@wicket.apache.org
Subject: Re: Behaviour.onInitialise()
On Thu, Feb 7, 2013 at 3:33 PM, Colin Rogers
colin.rog...@objectconsulting.com.au wrote:
That ambiguous
