[jira] [Commented] (WICKET-4444) Add a callback to the Session which is called when the HttpSession is invalidated

["Don Ngo (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259675#comment-13259675 ] 

Don Ngo commented on WICKET-4444:
---------------------------------

Martin,

I, for one, am very interested in a fix for this issue.  I've been struggling for months trying to find a work around. In fact, this issue is holding me back on rolling out my first wicket application.  Please consider putting this fix in ASAP.  I believe others are interested in having this fix as well.

Regards,

Don Ngo
                
> Add a callback to the Session which is called when the HttpSession is invalidated
> ---------------------------------------------------------------------------------
>
>                 Key: WICKET-4444
>                 URL: https://issues.apache.org/jira/browse/WICKET-4444
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.0.0-beta1
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>         Attachments: WICKET-4444.patch
>
>
> Currently the only notification that a user session has gone is org.apache.wicket.Application#sessionUnbound(String) which gives only the http session id as context.
> With the proposed change it will be possible to have an explicit callback method in o.a.w.Session itself. It will be called after explicit usage of Session#invalidate(Now)() or http session expiration due to inactivity.
> See the proposed patch.
> One "problem" is that now the http session attribute that holds the instance of SessionBindingListener will keep a reference to the Wicket session, but I think this should not cause bigger memory footprint because the same Session instance is already kept in another attribute in the http session, so the serialization process will just link the second to the first. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira