SOAP session scope
The idea of SOAP session is to have a transport-independent way of managing a session between two SOAP nodes; obviously, between the client and the server. Here, Axis2 uses SOAP headers in order to manage the session. In the SOAP session scope, it has a slightly longer lifetime than the request session scope, and deploying a service in a SOAP session is required to change
services.xml as well. Managing a SOAP session requires both the client and the service to be aware of the sessions, that is, the client has to send the session-related data if he/she wants to access the same session and the service has to validate the user using the session-related data.
SOAP-based session management is not interoperable; part of the reason ...