Title: setting cookie property in Call
Hi David,
i have no problems setting cookie using the following,
 
xyzServiceSoap._setProperty(HTTPConstants.HEADER_COOKIE,"ASP.NET_SessionId=SomeId" );
 
xyzServiceSoap is the stub generated by WSDL2Java in IBM's web services toolkit.I did not debug this, but there is no problem with the above statement, it works fine.I'll check if it sets the call throug call.setProperty. Did you verify your idea using TcpMon or a similar tool ?
Best Regards
 
-----Original Message-----
From: David Self [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 11:27 PM
To: '[EMAIL PROTECTED]'
Subject: setting cookie property in Call

I noticed that neither of the two following calls actually set the cookie from a Call object:

call.setProperty(org.apache.axis.transport.http.HTTPConstants.HEADER_COOKIE, "cookie_str");

or

call.getMessageContext().setProperty(org.apache.axis.transport.http.HTTPConstants.HEADER_COOKIE, "cookie_str");

I found the following message in the archives and tried its suggested solution, which works for me.  I didn't see a response to Doug's last question, so I was wondering if this is a bug that should be reported or if there is a more correct way to do this.

Thanks,
David

List: axis-user <?l=axis-user&r=1&w=2> 
Subject: Re: set cookie property <?t=103565158500004&r=1&w=2> 
From: Doug.Liao () alltelmd ! com <?a=103565152200005&r=1&w=2> 
Date: 2002-10-29 19:20:10 <?l=axis-user&r=1&w=2&b=200210> 
[Download message RAW <?l=axis-user&m=103591922029388&q=raw> ]

By examine the org.apache.axis.client.Call class implementation, I found that the cookie property set in Call object is not passed MessageContext object which is used in HTTPSender object. So I have made a patch to the Call invoke method as following:

msgContext.setProperty ( org.apache.axis.transport.http.HTTPConstants.HEADER_COOKIE, getProperty(org.apache.axis.transport.http.HTTPConstants.HEADER_COOKIE));

Should we report this as bug or there is a right way to set cookie property?

Thanks, Doug (904)854-5613

Reply via email to