I'm quite new to Wicket, so maybe my question will seem stupid. I need to ask sth to aviod reinventing the wheel.
In my application there is a few navigation components which create links for pages. Some pages have ajax-nature, some not. I'm trying to achieve preserving some page properties per user/browser/window session. For example searchBox content, data views current page and/or items per page. It's just to give user convenient tool - if users modify some view parameters, I expect they want to keep them not touched between navigation hops, similar to switching between apps in OS. I see two possibilites: instead of creating new page, recall the last page instance from session or somehow persist properties in session and restore them when page is created. The first option anyway will fail with Ajax pages as Wicket doesn't store modification performed with Ajax (am I right?) Is there any best practice? Has anybody tried to get functionality like that? I remember that in Tapestry there is annotation to achieve that - do we have/plan similar in Wicket? Please help me find a way in this dense fog :) Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
