Jens, That indeed could be dangerous (if the subclass implementation refers to subclass state that will not be initialised yet) - you can addOrReplace the returned component in onBeforeRender. This solution is nothing to do with the wicket:child/extension inheritance by the way, that will still work as per normal. You're just asking the children to supply some component the super-class will place in its bit of the markup (ie outside of wicket:child).
Does that make sense? Regards - Cemal jWeekend OO & Java Technologies, Wicket Training and Development http://jWeekend.com mcbain wrote: > > 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 | m...@jens-zastrow.de > web | http://jens-zastrow.de > xing | http://www.xing.com/profile/Jens_Zastrow > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://www.nabble.com/Page-inheritance-problem-tp25776777p25777065.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
