Ravi, Thanks anyways. It was my oversight. I didn't realize the list is being used for both Axis1 and Axis2. Sure explains some of the confusing messages I see when I was searching in the archives tough.
--Alex > -----Original Message----- > From: Ravi Krishnamurthy [mailto:[EMAIL PROTECTED] > Sent: Monday, January 08, 2007 6:10 PM > To: [email protected] > Subject: Re: Http session from client side... > > Alex: > Yes I was mentioning it in context to Axis1. > > I have not played with Axis2 yet. > > regards, > Ravi > Alex Huang wrote: > > Ravi, > > > > Thanks for the quick reply. I don't see any call object in the stub > > code. I remember call was in Axis 1.x. Is that what you > are referring > > to? > > > > Looking at the generated stub code, I decided perhaps the > best thing to > > do is calling OperationClient.getOptions().setManageSession(true). > > However, that didn't do anything at all. Snoops showed that the > > JSESSIONID was not added in the subsequent request. > > > > What else can I do here? > > > > Any help will be much appreciated. > > > > --Alex > > > > > >> -----Original Message----- > >> From: Ravi Krishnamurthy [mailto:[EMAIL PROTECTED] > >> Sent: Monday, January 08, 2007 4:47 PM > >> To: [email protected] > >> Subject: Re: Http session from client side... > >> > >> Alex: > >> May be try to set the call.setMaintainSession(true) in the > stub code > >> when the call object is created. > >> > >> regards, > >> Ravi > >> > >> Alex Huang wrote: > >> > >>> Hi All, > >>> > >>> I'm interfacing with a webservices server that returns a cookie > >>> Set-Cookie: JSESSIONID=C940DECC375E991239EE6A4F80304CB0 > in my login > >>> request and expects that I set that cookie in the > >>> > >> subsequent requests. > >> > >>> > >>> I have used wsdl2java to create the client libraries and made the > >>> login request using the client stubs generated. However, > I can not > >>> figure out how to get the HTTPSession back to retrieve this > >>> > >> cookie. I > >> > >>> tried using MessageContext.getMessageContext() but it > >>> > >> returns a null > >> > >>> pointer back to me. > >>> > >>> Searching on the archives reveals that > >>> MessageContext.getMessageContext() should work if it's on > >>> > >> the server, > >> > >>> but what about the client? > >>> > >>> Thanks for any help you can give. > >>> > >>> --Alex > >>> > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
