That's the problem. Session.bind() isn't called. I put a breakpoin in
AbstractHttpSessionStore.bind() but still it's hard to tell what's causing
this to be called...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome
-with-stateless-pages-in-Chrome-tp4659106p4659122.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
on earth
this happens exclusively with Google Chrome (in case it's symptomatic of
some other undetected problem).
Any ideas?
Thanks,
Anthony
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome-tp4659106.html
Sent from the Users
?
Thanks,
Anthony
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome-tp4659106.html
Sent from the Users forum mailing list archive at Nabble.com
How would I check this? I disabled Predict network actions to improve page
load performance but that hasn't changed anything.
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome-tp4659106p4659111.html
Sent from
-5-2013 15:59, schreef ChambreNoire:
How would I check this? I disabled Predict network actions to improve page
load performance but that hasn't changed anything.
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome