On Sunday 04 November 2007 02:37:39 Johan Compagner wrote:
> You just should call super of the same constructor you are in.
> just give the super call everything you got. If you got a model, give it
> but you don;t have to you can set it in the constructor with setModel
> afterwards.
That's what I do. But it makes my code look like those super calls have
different logic unless you know they are similar.
> I still don't get what this discussion is more about
I was trying to say that in my view this would be more readable.
protected WebPage(final IPageMap pageMap)
{
this(pageMap, null);
// commonInit();
}
protected WebPage(final IPageMap pageMap, final PageParameters parameters)
{
super(pageMap, parameters);
commonInit();
}
> If you really want to have an init phase thats called after the constructor
> is called (and finished)
> then i think you should choose a different web framework, That uses managed
> components/pages
No, I didn't mean that. I like wicket :)
Dima
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
