Re: Component Instantiation Listener Problem
Exactly what I needed. On Mon, Mar 8, 2010 at 12:04 PM, Igor Vaynberg wrote: > yes it is intended. you are not really meant to mock with the class > because the listener is called before the constructors of your > subclasses have finished. > > there are listeners you can use that are called in onbeforerender of > components where you can mock with the actual component instance, not > just the class. > > -igor > > > On Mon, Mar 8, 2010 at 8:36 AM, Ben Tilford wrote: >> I ran into an issue with a Component Instantiation Listener because the >> listener is notified before setModelImpl is called. Is this the intended >> behavior? It limits what you can do in your listener quite a bit. >> > > - > 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
Re: Component Instantiation Listener Problem
yes it is intended. you are not really meant to mock with the class because the listener is called before the constructors of your subclasses have finished. there are listeners you can use that are called in onbeforerender of components where you can mock with the actual component instance, not just the class. -igor On Mon, Mar 8, 2010 at 8:36 AM, Ben Tilford wrote: > I ran into an issue with a Component Instantiation Listener because the > listener is notified before setModelImpl is called. Is this the intended > behavior? It limits what you can do in your listener quite a bit. > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Component Instantiation Listener Problem
I ran into an issue with a Component Instantiation Listener because the listener is notified before setModelImpl is called. Is this the intended behavior? It limits what you can do in your listener quite a bit.
