[
https://issues.apache.org/jira/browse/WICKET-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538588
]
Johan Compagner commented on WICKET-1002:
-----------------------------------------
are you saying you also want this for temp sessions?
So we have to call onDestroy everytime a session is detached but is still a
temp?
But you just have to implement HttpSessionBindingListener on your WebSession.
We already have a HttpSessionBindingListener but that calls
Application.sessionDestroyed(sessionid)
Because you can't access the attrbute anymore.
So that can only happen from the inside.
Should we have our own WebSession implement HttpSessionBindingListener?
and then call onDestroy() or something like that? That we also call for a temp
session when it is detached?
You can easily do this yourself ofcourse.
> 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.
