[jira] Updated: (AXIS2-4714) Session management in Axis2 Service Client not working when only in-only operations are executed

["Anjana Fernando (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anjana Fernando updated AXIS2-4714:
-----------------------------------

    Attachment: Axis2Patch-4714.patch

This patch fixes the session management issue with in-only operations, by setting the transport headers for HTTP 202 codes.

- Anjana.

> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org