By default wicket doesn't send the no-store Cache header, so the page should be pulled from cache on back button. It's weird that the page is reloaded.
Anyway, new instance is created because there is a bookmarkable url. To creating new instances you'll have to either make the url non-bookmarkable (with the wicket:interface part), or you can mount the page using HybridUrlCodingStrategy (such as the ajax exampels are). To use this strategy you need the most recent wicket from trunk. -Matej On 8/1/07, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote: > Ummh .. quite interesting. > > I was supposing that Wicket disable browser caching by default, for > Bookmarkable page also. Isn't it Igor? > > Or is there any special API to enable/disable page caching on client side? > > Paolo > > > On 8/1/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > On 8/1/07, Fabio Fioretti <[EMAIL PROTECTED]> wrote: > > > > > > > > > This is because, when I push the back button, /mypage?user=ME url is > > > loaded, the constructor gets called and a new page is instantiated > > > instead of displaying the old instance (I presume). Is there a way to > > > avoid this page re-instantiation? > > > > > > why is that url loaded again on backbutton? it should come from browser > > cache, do you add a no-store header or something? > > > > also see HybridUrlCodingStrategy, that might help > > > > -igor > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
