[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12373076 ]
Deepal Jayasinghe commented on AXIS2-532: ----------------------------------------- I went though the patch and understood that you have done a great job , thx for doing all those. I have few question to clarify. We have transport independent session management called SOAP session , so if you deploy a service in a SOAP session scope then service will have transport independent session management. So there what will happen is ; when you deploy a service in SOAP session , when a service get a request it will send a serviceGroupID (which is the session ID) back , so if user send that back (in the next request) then user will be able to come back to the same session. In the meantime we have transport dependent session as well , both in simple HTTP server case and AxisServlet case we do support transport dependent session management. I think I am missing something please explain to me , the difference between what we have right now and what you have done. One other thing I understood from your path is that you can achieve the same goal by adding an axis2 module (.mar) , since what you have done is getting the session at the in handler and adding session id into outgoing message. So the best thing you should do is get the session by In handler and populate MessageContext using that. > Session Management > ------------------ > > Key: AXIS2-532 > URL: http://issues.apache.org/jira/browse/AXIS2-532 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Versions: 0.95 > Reporter: Rajith Attapattu > Attachments: session_march_28.patch, session_mgt_march29.patch, > session_mgt_march30.patch, session_mgt_march31.patch > > Session Management > ------------------------------- > This patch containes transport independent session mgt using WS-Addressing > EPRs > Interfaces > -------------- > All interfaces are located in the core module > Main interfaces useful for users > org.apache.axis2.session.Session > org.apache.axis2.session.SessionManager > org.apache.axis2.session.SessionIdFactory > There is a Null impl for these interfaces within core > Implementation > ------------------------ > All implementation specific classes are located in the session module > Clustering impl > ---------------------- > Clustering impl is located within the clustering module > (only empty classes so far) > Examples (located in the samples module) > ----------------- > ATM example > sample.session.atm.* > Echo example > sample.session.echo.* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
