ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "FrontPage/Axis2/SessionMgmtProposal" by RajithAttapattu
Date Wed, 05 Apr 2006 17:17:26 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by RajithAttapattu:

  Based on Srinaths comments and disscussion threads the initial proposal of UserContext was
discarded and an independent Session Management module was introduced.
  It's a layered architecture with 4 main interfaces.
- Session
+  1. Session
- SessionManager
+  2. SessionManager
- SessionIdFactory
+  3. SessionIdFactory
- SessionManagerFactory
+  4. SessionManagerFactory
+ Two handler will intercept the in and out pipeline. The handler in the in pipeline will
retrive or create a session based on the precense or absence of a session id.
+ The handler in the out pipeline will denote end of request and will mark the session for
  The idea was to enable the extention of the session model to support fail over and clustering
  There is a code and documentation patch provided in JIRA and discussions are going on in
the mailling list.
@@ -86, +90 @@

  " It is intended to be used as a building block by other specifications that require session
constructs -- in fact, several specifications related to transaction protocols in OASIS are
already building on WS-Context"
  If this claim is true we will be best placed using the WS-Context approch. See 3.2. Web
Services Sessions using WS-Context. RM WS-AT and WS-Coordination people can you verify?
+ --------
+ The new proposed strucutre can easily add a layer to implement WS-Context

View raw message