Hmmm...
this effectivly not uses the <wicket:child/> thing for the "inner"-subclass-components.
If i do so, from the Java-side its really bad to invoke "subclass-methods from
super-contructors".
Can the invocation of the getThatPanelIWantAlwaysButAtCertainLocation() method be deferred
somehow??
Regards
Jens
Jens,
Your super class could declare an
abstract protected void getThatPanelIWantSometimes()
method that the children can then implement to return whatever they like and
then the ball's back in the parent's court.
Regards - Cemal
jWeekend
OO & Java Technologies, Wicket Training and Development
http://jWeekend.com
jWeekend schrieb:
--
dipl. inform jens zastrow
phone | +49.152.04840108
mail | [email protected]
web | http://jens-zastrow.de
xing | http://www.xing.com/profile/Jens_Zastrow
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
