Hi!
Ok, so just to confirm: your original post states that you see a bound
wicket session when loading a stateless page with google chrome, but
Session.bind() is never called?
For as far as I know when wicket binds a sessions it always does so
through Session.bind(). So if that is not called, there's another piece
of code outside wicket which binds the session.
Do you have any other servlets or servlet filters in place?
How do you know a wicket session is bound?
And how are you checking if Session.bind() is called?
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 29-5-2013 8:36, schreef ChambreNoire:
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-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
