Session store (v4.3)
WebContext is an abstraction to deal with the HTTP request and response.
To specifically deal with the session, it relies on a
SessionStore which may be available via the
SessionStore has the following methods:
getOrCreateSessionId: gets or creates the session identifier and initializes the session with it if necessary
- ` get`: gets the attribute from the session
set: sets the attribute in the session
destroySession: destroys the underlying web session
getTrackableSession: get the native session as a trackable object (for back-channel logout)
buildFromTrackableSession: builds a new session store from a trackable session (for back-channel logout)
renewSession: renews the native session by copying all data to a new one.
For example, the
JEEContext currently uses the
JEESessionStore which relies on the JEE session. In Play, we have a specific cache-based
PlayCacheSessionStore as well as in Knox, which has a cookie-based