[
https://issues.apache.org/jira/browse/AXIS2-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-4714.
-------------------------------------------------
Resolution: Fixed
applied the patch with revision 944582
> Session management in Axis2 Service Client not working when only in-only
> operations are executed
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4714
> URL: https://issues.apache.org/jira/browse/AXIS2-4714
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Anjana Fernando
> Fix For: nightly
>
> Attachments: Axis2Patch-4714.patch
>
>
> When using Axis2 Service Client to access a web service in transport session
> scoped services (by using 'Options.setManagedSession(true)'). If the
> operation called from the Service Client is an in-only operation, the session
> is not kept.
> This is because, when an in-only operation is called, the HTTP response code
> is 202, where by default, in the transports, when only the code is 200, the
> transport headers are set and the response it processed. So since headers are
> not set in 202 code situations, the session cookie is not again set in
> subsequent operations from the Service Client.
> Cheers,
> Anjana.
--
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]
