Certainly, parameters are just name of object class and object code/id. But actually I'm saying that I can create store PageReference with its related PageParametes in session and using PageParameters from the request to obtain a Page instance from page store. The only thing I'm not sure is the lifecycle of values in such a cache.
AFAK overriding page factory is the only way how to make a page singleton in the session. There are plenty of pages that should behave as singleton. There would be the other way if it was easy to split Tree and its DYNAMIC state. Unfortunately tree is very difficult in restoring its state. The user don't want to expand tree items every time she has to return back to the page. Alexandru Objelean wrote: > > If you can restore the page state from passed PageParameters, then it is > doable... > > Alex Objelean > > -- View this message in context: http://www.nabble.com/how-to-create-a-BookmarkablePageLink-for-the-particular-page-instance-tp24659102p24659535.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
