[ http://issues.apache.org/jira/browse/SYNAPSE-44?page=comments#action_12454569 ] Sanjiva Weerawarana commented on SYNAPSE-44: --------------------------------------------
The problem is the second paragraph: that Synapse is dropping reference parameters. Why??? That's just plain wrong. Copying the serviceGroupId header thru may work for this but will not work for other application defined session headers etc. (for example like a secure conversation session). WSA ref props are meant to be opaque outside of the creator and we cannot break that rule. > Synapse does not handle SOAP sessions correctly > ----------------------------------------------- > > Key: SYNAPSE-44 > URL: http://issues.apache.org/jira/browse/SYNAPSE-44 > Project: Synapse > Issue Type: Bug > Components: Core > Reporter: Chathura Ekanayake > > 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. - 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
