If the previous page is bookmarkable you don't need to keep a reference to the page instance; instead, just re-create the page parameters and call setResponsePage(pageClass, parameters) when the user clicks Cancel.
jk On Wed, Nov 26, 2008 at 01:35:11AM -0800, jhp wrote: > > Well, yes references to pages seems to be given as constructor arguments to > several pages. The idea is that if 'Cancel' is clicked, application goes > back to previous page. The possibility to go back more than one page is not > necessary. Is the correct way to implement cancle with some javascript that > does something like user clicking previous page? > > Jukka > > > Martijn Dashorst wrote: > > > > With Wicket 1.3 only one page should be stored in session. You should > > check if you don't keep references between pages -> that would result > > in 1+N pages (with N being the number of pages you reference in your > > page). > > > > Other than that: using LDM's and DataView/DataProvider instead of > > ListView will help considerably. > > > > Martijn > > > > > > -- > View this message in context: > http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697523.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
