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 an older instance, you can use Component#reAttach
Eelco On 10/5/06, Jaime De La Jara <[EMAIL PROTECTED]> wrote: > What could be the preferred way to have an application with tabs and have a > bunch of pages inside one of the tabs so the navigation between them is > equivalent as a navigation between standalone pages? Besides of extending > from Panel, What would be the analog of setResponsePage() ? > > Thanks. > > Jaime. > > > ________________________________ > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates > starting at 1ยข/min. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
