[
https://issues.apache.org/jira/browse/SYNAPSE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-227.
---------------------------------
Resolution: Fixed
Assignee: Upul Godage
There is a mediator which provides a simple session service in the ESB site at
http://esbsite.org/
The session mediator has to be at the ends of the incoming and outgoing message
flows in the Synapse configuration. In the incoming message flow, it will read
the cookie and store the session ID as a message property. In outgoing message
flow, it will take the message property and write it as a cookie.
In the custom mediators session can be retrieved by
org.apache.synapse.mediators.session.Session session =
org.apache.synapse.mediators.session.SessionMap.getSession(messageContext,
true);
Session object has the Map interface to get() and put() objects. A separate
thread cleans up the timed-out session objects.
There is a sample at the site.
http://esbsite.org/resources.jsp?path=/mediators/upul/Session%20Mediator
> Session-based custom mediator.
> ------------------------------
>
> Key: SYNAPSE-227
> URL: https://issues.apache.org/jira/browse/SYNAPSE-227
> Project: Synapse
> Issue Type: Improvement
> Components: Extension Mediators
> Reporter: kumaran venkatesan
> Assignee: Upul Godage
>
> In a web based application tracking the user based on session is important.
> If the synpase supports session-based custom mediators, it will be useful to
> incorporate in the applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
