Hi In my opinion, when you use lots of inheritance in a page, its really imposible to control if a component appears just once in the page. Wicket is great for the ability to reuse components. Actually I've been able to create a private framework where I'm able to build an entire page with components binded to a JPA entity bean just with some annotations (amazing productivity). If the project gets complicated, I think there is no possible way to control the uniqueness of the component in the page. The advantages of adding a component wherever you cant along the hierarchy are true, I don't think that your proposal gives the best of both worlds. Regards