you can roll that, just use the beforerenderlistener you can install in the application subclass.
-igor On Mon, Apr 28, 2008 at 8:03 AM, James Carman <[EMAIL PROTECTED]> wrote: > On Mon, Apr 28, 2008 at 10:58 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > 2008/4/28 Uwe Schäfer <[EMAIL PROTECTED]>: > > > > > James Carman schrieb: > > > > > > > > > > > > > Or, perhaps Wicket could add in some lifecycle method annotations? > > > > > > > > > > pleeeeeeease don´t! > > > > > > using annotations for this kind of lifecycle methods is a simple abuse > of > > > them. non-obvious order, inheritance etc... lesson learned from jpa,ejb3 > > > etc... > > > > no worries. we are not going to do this. at one point we had > > @OnBeforeRender, @OnAfterRender, @OnDetach and a couple of others all > > working in the 2.0 branch. we didnt like it. the code became a lot > > less self-documenting, and in the end you still ended up overriding > > existing methods a lot of the times so there was no benefit. > > > > That's true. Most folks would just pick a method name and stick with > it for all initialization. So, this wouldn't buy you much. An > interface-based approach might, though. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
