[Wicket-user] Style of development (many web pages vs many panels)

[Kenneth Foo]

Hi   Just curious here as to which is more "correct"   Was trying out wicket and noticed that i have a tendency to design apps where there are few pages (2 or 3 WebPage objects), and many more panels (navigation panels, main content panel, header panel). The main content panel would then be interchanged with the necessary "module" panels.   (eg. if I click on a "user management" link in the navigation panel, I'll swap what's in the main content panel with the user management panel. In this user management panel, I'll have a "user listing" panel, an "edit user" panel, etc which I'll swap depending on which one i'm interested to use. The responsibility of swapping belongs to the parent container which decides on what to swap with based on the events fired by the subpanels)   In this model,each page has 1 form, and within this form, I have panels of modules (such as user management module, etc...). Panels nest with other panels, sometimes up to 3-5 levels deep.   I'm curious whether others are using this method (which I feel is more "componentized), or the more traditional web-style approach where we have many pages (eg. one page for user listing, one page for editing user details, etc) and transferring navigation to these pages via redirects/etc or requestCycle.setResponsePage().   Off the top of my head, using panels instead of web pages allows me to reuse the "user management" module in other web apps or for quick prototyping.   What are your thoughts, guys?     Regards Kenneth