On 10/04/2012 10:24 AM, Martin Grigorov wrote:
Hi Martin
What really matters for this functionality is whether the page itself
is versioned. By default all pages are versioned - see
org.apache.wicket.settings.IPageSettings#getVersionPagesByDefault.
page is versioned, form is explicitely set versioned, FormComponents do the
modelChanging()
...
modelChanged()
dance. (Simple radios)
it looks like any form submit is just applied to the last page version,
instead of previous ones.
p1
p2
p3 <- back btn
p2 <- sunmit
p4 altering the state of p3
the form is submitted by a simple javascript:form.submit() call.
GET vs POST does not make a difference.
the page itself comes back with a 302
HTTP/1.1 302 Found
Server: Resin/3.1.8
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Location: http://192.168.1.218:8081/project?6
Content-Type: text/html
Content-Length: 73
Date: Thu, 04 Oct 2012 08:48:22 GMT
and then with the page
HTTP/1.1 200 OK
Server: Resin/3.1.8
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 04 Oct 2012 08:48:23 GMT
Please describe what you do in the page and what is the result when
you go back. What is different between FF and Chrome ?
Check whether the browser doesn't use its cache when you go back.
a sysout on oBR indicated, that the page is rerequested every time.
let me know whatever additional info i can provide.
cu uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
