John Patterson wrote:
>
> The counter example was the exact mistake that is very easy to make when
> designing a component that can be extended. So easy to make that even the
> mighty super genius Igor initially did it in PagingNavigation. So most
> mere mortal wicketeers could not be expected to understand this intricacy.
> Your assumption is that the subclass can return its result without access
> to parameters passed into the constructor. Even getTitle() may need to
> access a domain object passed on creation.
>
Sorry, my smug reply was wrong and you were right. So that first rule should
be: never call an overridable method form the constructor; your example is
not calling the overridible method from the constructor... it simply
provides a class that can do so later (from render). Exactly as Igor said
earlier.
Note to self: don't post messages when half cut. But I have to break that
rule just one more time
--
View this message in context:
http://www.nabble.com/Alternative-method-to-initialise-page-tp16742636p16917444.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
