Github user svenmeier commented on the issue:
https://github.com/apache/wicket/pull/233
Currently HttpSessionStore and PageStoreManager each use their own instance
of HttpSessionBindingListener.
Yes, we might be able to unify these. But with a simple fix we don't
introduce even more - possibly faulty - changes.
It was unfortunate that we didn't consider all possible callbacks from
Servlet containers when this problem started with WICKET-6356.
IMHO we should go with the simplest fix: Prevent anything bad from
happening, when re-setting the session attribute:
- clustering will work (because the attribute is re-set)
- it doesn't matter whether the container calls valueBound() or not
- if the container calls valueUnbound(), it does nothing bad during
storeTouchedPages()
Andrea, what do you think?
BTW do we have to take care of concurrent access to the SessionEntry? I see
that Martin used an AtomicBoolean, but how does that help if there are two
request simultaneously storing touched pages?
---
