axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2282) Session Management not supporting different session identifiers (e.g. ssnid)
Date Thu, 28 Jun 2007 10:14:26 GMT

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

Deepal Jayasinghe resolved AXIS2-2282.
--------------------------------------

    Resolution: Fixed

By default we support JSESSIONID , if someone wants to have custom session cookie id then
he need to set the following property with value as cookie name.
  option.setOption(Constants.CUSTOM_COOKIE_ID);

> Session Management not supporting different session identifiers (e.g. ssnid)
> ----------------------------------------------------------------------------
>
>                 Key: AXIS2-2282
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2282
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>            Reporter: Thomas Michelbach
>            Assignee: Deepal Jayasinghe
>            Priority: Blocker
>             Fix For: 1.3
>
>
> I'm having a problem with session using a Service Client. I have two methods calling
two different operations of a web service. The webservice is not implemented in axis2. 
>  
> I need to use a session so the web service can identify the axis2 client by each call.
>  
> My class defines a single ServiceClient to make two different call.
>  
> It has following option turned on:
> client.getOptions().setManageSession(true );
> When I make the first call to the server, it runs the webservice and responds correctly.
Following header is then passed:
>  
> HTTP/1.0 200 OK
> Set-Cookie: ssnid=4383SO95jARAuR1Ad3Cc6clMdI1KEQo-555562; path=/;
> Content-Type: text/xml;charset=utf-8
> Connection: Keep-Alive
> Content-Length: 646 
>  
> By the second call the client does not put the session data back to identify itself.

>  
> So it passes only this information:
>  
> SOAPAction: "urn:anonOutInOp"
> User-Agent: Axis2
> Authorization: Basic [based64usernamepassword]
> Host: localhost:5554
> Content-Length: 453
> Content-Type: text/xml; charset=UTF-8
> This was posted to the user mailing list and the conclusion was that axis2 does not support
ssnid as session id. So a axis2 client can't communicate with another application server using
session management.

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


Mime
View raw message