Wicket, page stack, and memory usage

A Wicket application serializes and caches all pages to support stateful components, as well as for supporting the back button, among other possible reasons. I have an application which uses setResponsePage to navigate from screen to screen. Over a pretty short amount of time the session gets rather large because all of the prior pages are stored in the session. For the most part, I only need the session to contain the current page, for obvious reasons, and perhaps the last 2 or 3 pages to allow easy navigation using the browser's back button.

Can I force a page to expire after I have navigated away from it and I know that I don't want to use to back button to that version of the page? More generally what is the recommended way to deal with session growth in Wicket?

From stackoverflow

• http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-td20697077.html

  If you use loads of domain objects on your page, which are eventually tightly coupled to other domain objects, be sure to avoid serialization for these!

  Have a look at LoadableDetachableModel for wrapping domaing objects DataView and IDataProvider for displaying list of domain objects

  Thou shalt not stuff domain objects into instance variables of components. Thou shalt not make domain object references final in order to use them in anonymous subclasses. Thou shalt not pass a mere List of domain objects to a ListView.

  Perhaps, when subclassing WbeRequestCycle in your Application class, you might gain control of a page's lifetime in the pagemap... haven't tried it, though