I don't know if there is a another way; but it is consistent
abstract Class TopMost_Parent {
abstract void methodZ();
}
abstract Class SubParent extends TopMost_Parent {
public void methodZ() {.....};
abstract void methodY();
}
class Class Child extends SubParent {
// Should Child implement methodY() ???
}
SubParent is a "Sub" at the end so it should use <wicket:child/> when you
compare it with OOP it is consistent, right ?
Altuğ
2010/10/4 LutherBaker <lutherba...@gmail.com>
>
> TopMost_Parent
> <body>
> <wicket:child/>
> </body>
>
>
> SubParent extends TopMost_Parent
> <body>
> <wicket:extend>
> blah blah
> </wicket:extend>
> </body>
>
>
> Child that needs to add no markup
> Nothing seems to work
>
>
> To get this to work, I end up doing this:
>
> SubParent extends TopMost_Parent
> <body>
> <wicket:extend>
> blah blah
> <wicket:child/>
> </wicket:extend>
> </body>
>
>
> Child that needs to add no markup
> <body>
> <wicket:extend> </wicket:extend>
> </body>
>
>
> I understand I need child.html markup ... but do I need to <wicket:extend>
> inside of it? and do I need to include <wicket:child/> in the SubParent?
>
> -Luther
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/What-is-the-correct-way-to-extending-a-window-if-I-ve-not-content-to-add-tp2954955p2954955.html
> Sent from the Users forum 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
>
>
