[
https://issues.apache.org/jira/browse/WICKET-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799103#comment-13799103
]
Christoph Leiter commented on WICKET-5390:
------------------------------------------
That's the jetty discussion:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=408167
If Wicket always return false in SessionEntry#equals then Jetty will store the
page in the DB every time which is also not ideal.
> Session management doesn't work with Jetty's JDBCSessionManager
> ----------------------------------------------------------------
>
> Key: WICKET-5390
> URL: https://issues.apache.org/jira/browse/WICKET-5390
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.11.0
> Reporter: Christoph Leiter
>
> I use JDBCSessionIdManager/JDBCSessionManager from Jetty to store my sessions
> in a DB. Jetty tries to be smart and determines if a session is dirty and
> only persists it then. The logic is that a call to HttpSession#setAttribute
> may cause the dirty flag to be set if A) the value is new OR B) the value is
> changed, i.e. not #equals to the previous value. Wicket stores a
> PageStoreManager$SessionEntry as an attribute. This class doesn't have a
> specific equals implementation and so from the Jetty point of view the
> session never changes. The effect is that after Jetty restores the session
> from the DB it will be always in the initial state.
> One possible fix is to always return false in SessionEntry#equals. But I'm
> not sure what Jetty is doing here is correct either.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
