Kumaran
The requirement is to have *Stateful *mediation configuration. Each
service request from the client will be passed through the
Synapse and need to do basic verification like Session checking and
Funcational Access Profile checking(FAP) before the request
sent to the EPR’s deployed on different hosts.
Ok.. as Paul mentioned, when using the NIO transport you will not be
able to get access to a http servlet session from within Synapse - i.e.
it simply doesn't exist. However, as I said earlier, your custom
mediator can store session (i.e. say a local HashMap etc) where you
could co-relate messages with the same WS-A MessageID, or http cookie ID
etc and get access to the stored information. Also this map could be
shared over a cluster (like J2EE session replication) using the Axis2
clustering support virtually without any custom coding. Thus I guess to
satisfy your basic requirement, you will create a Map within your
mediator, and use the above to simulate the http sessions
asankha
