[
https://issues.apache.org/jira/browse/WICKET-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782054#comment-13782054
]
Paul Bors commented on WICKET-5380:
-----------------------------------
Proposed fix was also tested on GlassFish 3.1.2.2 which works just as well as
GF 4.x
> Wicket rebinds the SessionEntry session attribute and this causes problems in
> Glassfish
> ---------------------------------------------------------------------------------------
>
> Key: WICKET-5380
> URL: https://issues.apache.org/jira/browse/WICKET-5380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.11.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 7.0.0, 6.12.0
>
>
> With WICKET-5164 Wicket made
> org.apache.wicket.page.PageStoreManager.SessionEntry a
> javax.servlet.http.HttpSessionBindingListener to be notified when this
> session attribute is removed to be able to clean the disk data store when the
> session is replaced.
> This causes problems on Glassfish server (ver. 3 and 4) because GF notifies
> the HttpSessionBindingListener no matter whether the new value is different
> from the old one.
> Jetty and Tomcat check the new against the old value by identity and there is
> no problem.
> See this mail discussion for more details:
> http://markmail.org/thread/uigzwllvib2iohvu
--
This message was sent by Atlassian JIRA
(v6.1#6144)
