Regarding the commented out no-store, any idea why the wicket core developers
didn't used it directly ? Having a consistent behavior across browser + ajax
and back button working seem rather good. I wonder why it isn't included
currently.
joseph
_
From: Craig McIlwee [mailto:craig.mci
As long as you prevent the browser from caching the page with the form (just
the page itself, caching the resources is fine) then when the user hits back
wicket will pull the old page instance from the pagemap and rerender it. That
page instance is the same one that was used the first time, so
