[
https://issues.apache.org/jira/browse/WICKET-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538597
]
Eelco Hillenius commented on WICKET-1002:
-----------------------------------------
We can't really guarantee this, since we don't guarantee that the session is
bound to HttpSession, and the ISessionStore doesn't 's unbind method doesn't
take the session object but rather the session id (and that is because of how
the servlet API works).
Implementing this yourself should be trivial, and has the advantage that you
don't have take the generic API into consideration.
> Add lifecycle methods for Session
> ---------------------------------
>
> Key: WICKET-1002
> URL: https://issues.apache.org/jira/browse/WICKET-1002
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Reporter: Thomas Mäder
> Fix For: 1.3.0-beta5
>
>
> Currently, there is no standard way to track the lifecycle of a
> org.apache.wicket.Session instance. This, however is useful when the Session
> object has to initialize/deinitialize, for example, to register listeners
> with a domain model, etc.
> I propose the introduction of an Session.onDestroy() method like on
> Application.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
