[jira] Updated: (WICKET-1002) Add lifecycle methods for Session

["Thomas Mäder (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mäder updated WICKET-1002:
---------------------------------


Yes, I could implement HttpSessionBindingListener  in the Session and have my own request cycle, but I see a couple of drawbacks to this:

1) it only works for non-temporary sessions. 
2) It depends on the exact implementation of the session store

I guess you can always work around the temporay-session problem, but I just think the init in the constructor/deinit in "onDestroy" would make client code so much easier to understand.

> 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
>
> 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.