what about custom IModel impls ? it will work automatically for all IModel impls provided by Wicket, but will not work for custom ones. And then the users will start creating tickets ...
On Thu, Sep 23, 2010 at 12:16 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Well you could have your hierarchy of classes and on your base class call > > getApplication().notifyComponentInstantiationListeners(this); > > As component does. > > Ernesto > > On Thu, Sep 23, 2010 at 12:11 PM, James Carman > <ja...@carmanconsulting.com> wrote: > > On Thu, Sep 23, 2010 at 5:46 AM, Ernesto Reinaldo Barreiro > > <reier...@gmail.com> wrote: > >> > >> So that other classes could use the same trick by implementing > IInstantiable ? > >> > > > > How, exactly, is Wicket going to know when they're instantiated? The > > only way the component instantiation stuff works is that the Component > > constructor does the notification. > > > > --------------------------------------------------------------------- > > 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 > >
