Version: wicket1.4.13
Is there any reason onInitialize would not be called? And is it always
called before onBeforeRender? When I look at my logs, it looks like
there are cases where onInitialize wasn't called. But onBeforeRender
was always called.
Berlin Brown
create a quickstart that reproduces this, oninitialize() should always
be called on components after they are added to the page.
-igor
On Thu, Feb 10, 2011 at 8:49 AM, Brown, Berlin [GCG-PFS]
berlin.br...@primerica.com wrote:
Version: wicket1.4.13
Is there any reason onInitialize would not be
On 2011-02-10 17:49, Brown, Berlin [GCG-PFS] wrote:
Version: wicket1.4.13
Is there any reason onInitialize would not be called? And is it always
called before onBeforeRender? When I look at my logs, it looks like
there are cases where onInitialize wasn't called. But onBeforeRender
was always
failing to do so will throw an exception.
-igor
On Thu, Feb 10, 2011 at 8:58 AM, Matthias Keller
matthias.kel...@ergon.ch wrote:
On 2011-02-10 17:49, Brown, Berlin [GCG-PFS] wrote:
Version: wicket1.4.13
Is there any reason onInitialize would not be called? And is it always
called before