RE: [Wicket-user] Replacing Page components in response to user input

[Frank Silbermann]

I can see the motivation for putting my replaceable components in a Panel if the HTML requirements differ.  Likewise, if I have enough components to replace that I'd rather not have to replace them one at a time.  But if it's just a single component that I'm replacing, is there really any need to put it in its own panel? panel is the basic piece of wicket composition. so you will use them often. for some situation (when the panel is not really reusable outside the page) you might want to use Fragments because they make things tidier and easier. -Igor   Yes, but if I have but a single <span wicket:id=”myDataTable”> in my HTML, and my Page is to replace my DataTable component with another, couldn’t I do without a separate Panel _or_ Fragment?   Why would I need _any_ special HTML container for my DataTable?    (Or are we saying the same thing in that, in its implementation, a DataTable _is_ a Panel?)