Hi Thomas; Please create a JIRA , seems like we need to support different session ids , at the moment we support JSSION but not ssnid.
Thanks Deepal > Hi, > > 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 the server 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. > Should it be able to use that Set-Cookie Information 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 > > There is also no new header for identification of the session. So the > application starts a new session and returns an error, because the > cached data is not available. > > Can someone help me? I'm using axis2 1.1.1 > > Bye and Thanks a lot, > Thomas > > > -- > Thomas Michelbach -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
