[
https://issues.apache.org/jira/browse/SYNAPSE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chathura Ekanayake resolved SYNAPSE-44.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0-RC1
Assignee: Chathura Ekanayake
This issue is resolved and now synapse copies wsa reference parameters
correctly. This fix is verified by a sample scenario involving a soap session
between Axis2 client and Axis2 server mediated through Synapse.
> Synapse does not handle SOAP sessions correctly
> -----------------------------------------------
>
> Key: SYNAPSE-44
> URL: https://issues.apache.org/jira/browse/SYNAPSE-44
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Chathura Ekanayake
> Assigned To: Chathura Ekanayake
> Fix For: 1.0-RC1
>
>
> Axis2 maintains SOAP sessions by using a SOAP header named ServiceGroupId.
> When a client invokes an Axis2 service with soap session enabled, Axis2 puts
> an unique ID for that session in the response as a reference parameter under
> the <wsa:ReplyTo> header. Then the client includes that ID in the subsequent
> requests so that the session can be maintained.
> Problem occurs when this scenario is executed with Synapse in the middle of
> the client and the server. Synapse drops reference parameters under the
> <wsa:ReplyTo> header. Therefore, client does not get the ServiceGroupId and
> the session will not be maintained.
> Synapse should copy the ServiceGroupId under the wsa:ReplyTo header in order
> for soap sessions to work.
--
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]
