ITab is a factory for tab panels - it is there as a level of indirection so you dont have to create/populate panels for each tab until the user selects the tab.there is nothing special you need for state management - wicket takes care of it for you.
to keep the state of previous tabs instead of alw
So, if I use the Panels approach I'd need just one page and the navigation inside a tab would be using the replace method of MarkupContainer right?, and in this case how could I manage state in each tab?One thing of TabbedPanel implmentation I don't understand is why tabs are added first to a list
yes, have everything be a panel. there is absolutely nothing wrong with that. wicket makes very little distinction between a page and a panel - a page is just a top level container.if you create a basepage or something similar you will lose previous state - like selected tab, etc. it is simly much
And in the case of a web app that handles, for example, invoices and vendors with this navigation flow : Invoice Search -> List of Invoices -> Invoice detail -> Invoice edition Vendors Search -> List of Vendors -> Vendor detail -> Vendor editionand I'd like to crea
To work with panels and component replacement. That way you would
hardly ever work with setReponsePage, but rather with
Component#replaceWith or MarkupContainer#replace in Wicket 1.2.x, or
in Wicket 2.0, you would just create the new component with the proper
parent or in case you'd want to reuse a
