OK. Thanks, I'll see if I can do it differently.
Eyal Golan [EMAIL PROTECTED] Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Mon, Nov 17, 2008 at 3:31 PM, Martijn Dashorst < [EMAIL PROTECTED]> wrote: > Don't share components across requests or even pages. You can't do that. > > Martijn > > On Mon, Nov 17, 2008 at 1:50 PM, Eyal Golan <[EMAIL PROTECTED]> wrote: > > Our application has a base page and we use markup inheritance. > > In the base page we have a headerWe call it HeaderPanel. > > HeaderPanel has MainTabsPanel, which consists with the menu links. > > > > The situation now is that for each page, the HeaderPanel and > MainTabsPanel > > are constructed in each page (because of the markup inheritance). > > This is what we have in the base page constructor: > > HeaderPanel headerPanel = new HeaderPanel("headerPanel", this); > > And this is in the HeaderPanel constructor: > > add(new MainTabsPanel("mainTabs")); > > > > For some reasons I want the MainTabsPanel to be constructed only once. > > > > So, instead of adding using new, I want something like: > > add(mySession.getMainTabsPanel()); > > or > > add(myApplication.getMainTabsPanel()); > > > > Which one is better or is there even something better than this? > > > > > > > > Eyal Golan > > [EMAIL PROTECTED] > > > > Visit: http://jvdrums.sourceforge.net/ > > LinkedIn: http://www.linkedin.com/in/egolan74 > > > > P Save a tree. Please don't print this e-mail unless it's really > necessary > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
