On 8/1/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > 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.
It really is, as it seems that every bookmarkable page isn't pulled from cache over here... > Anyway, new instance is created because there is a bookmarkable url. > To creating new instances I think you meant "to avoid the creation of new instances", didn't you? > 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. Ok, thanks a lot and thanks to all of you for your precious answers. Kindest regards, Fabio Fioretti - WindoM --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
