From: Christopher B. <bl...@gs...> - 2004-03-31 16:49:14
|
On Wed, Mar 31, 2004 at 10:26:49AM -0500, Calvin Hendryx-Parker wrote: > I ended up just using the wsdl2py code generation and it works fine. > If I get some more time I'll check into using the ServiceProxy with the > this weather service. They published it quite some time ago so I'm not > sure how maintained it is. Wow. That is *certainly* strange behavior. I looked at the request generated from ServiceProxy. It looked like: <ns1:GetWeatherInfo xmlns:ns1="http://ejse.com/WeatherService/"> <zipCode xsi:type="xsd:int">20782</zipCode> </ns1:GetWeatherInfo> Then I looked at the request generated from wsdl2py (Calvin - when you call locator.getPort(), you can pass tracefile=sys.stdout), and it looked like this: <GetWeatherInfo xmlns="http://ejse.com/WeatherService/"> <zipCode xsi:type="xsd:int">20782</zipCode> </GetWeatherInfo> To my eyes, these two requests are the same. I noticed that the server is running IIS and is ASP.NET - maybe their SOAP demarshaller is non-conformant? Anyone else on the list care to weigh in on this? > Thanks for all the help! Those debugging tips are what I needed to > keep diving deeper with the ZSI stuff. Yup - that's the great part about SOAP. A project I've been meaning to work on is a simple little GUI that allows you to punch in a SOAP request to send to the server. See if it works, and tweak your request until you get it right. > BTW great presentation at PyCon :-) Thanks. :) -c -- 11:10:01 up 121 days, 54 min, 25 users, load average: 0.00, 0.00, 0.00 |