tabbed panel is meant to be used with panels not with pages. so instead of having each tab be its own page, simply make it each own panel.
-igor On Wed, Apr 16, 2008 at 7:53 AM, byhisdeeds <[EMAIL PROTECTED]> wrote: > > I'm new to wicket and would greatly appreciate for someone to point me in the > right direction. I have an existing web application implemented using jsp's > that I'm trying to convert to wicket, where each page has a header section, > body section and footer section. The header section has a main tab and sub > tabs that must be shown for all pages in their exisiting state, that is, > indicating the existing selected state of the tab and subtab. > > I have started with the example using the TabbedPanel, but I'm having some > problems with the following. > > 1)The state of the tabs does not seem to be saved when I switch to other > pages which are not called from the tab. > 2)I cannot seem to embed the tab from these pages in other pages that will > be called from links of other abitrary pages. > > I'm not sure I've explained it but can someone point me towards a solution. > -- > View this message in context: > http://www.nabble.com/Shared-tab-component-across-pages-tp16722526p16722526.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
