Sharing wicket components between page is a very bad idea. You are about to open large can of very nasty worms. Just don't do it. Proper way is to "externalize" the navigation state from your component and store it in session. Write couple of detachable models that do that.
-Matej On Sun, Feb 1, 2009 at 10:08 AM, Per Newgro <per.new...@gmx.ch> wrote: > Hi, > > i would like to share (instance reuse) a navigation panel in my page flow. I > try to achieve that so i can keep the current state of navigation > components. It's a clone of the windows xp sidebar in system controls. > > But i don't know if sharing is a good idea. I will have many pages. What > happens if i create a new page, add the navigation panel of one page to the > next and redirect by using setResponsePage? > Will the last page be "garbage collected"? Normally java is only gc if no > references are present to an object. Is wicket doing it similar? > > Thanks 4 help > Per > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
