[ 
https://issues.apache.org/jira/browse/AXIS2-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502102
 ] 

Davanum Srinivas commented on AXIS2-2777:
-----------------------------------------

Point taken, that blog entry is irrelevent for this discussion. as 
vmware_soap_session is not supported by Axis1 either AFAIK.

thanks,
dims

> serviceClient.getOptions.setManageSession(true) option does not keep all the 
> cookies / No way to access HTTP Transport headers in Axis2
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2777
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2777
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: transports
>    Affects Versions: 1.2
>         Environment: Windows XP Professional 
> JDK1.5
> Axis2 1.2
>            Reporter: Serdar Badem
>            Assignee: Deepal Jayasinghe
>
> I am trying to use Axis2 to access some 3rd party web services which happens 
> to use Set-Cookie in the HTTP Header (Which gets filled in once successfully 
> authenticated) and manages the session that way.
> Axis2 does not allow any way to access to the HTTP Header from the 
> MessageContext. When I use the 
> serviceClient.getOptions.setManageSession(true)  option it seems like this 
> option only stores the selected items in the header :
> HTTPConstants.HEADER_SET_COOKIE
> HTTPConstants.HEADER_SET_COOKIE2
> and ONLY the cookies with the following names: 
> Constants.SESSION_COOKIE or
> Constants.SESSION_COOKIE_JSESSIONID
> which is very limited. We need a better way to support Cookies or more 
> generically make the fields in the HTTP Header available to the client from 
> the MessageContext.

-- 
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]

Reply via email to