<br><br><div><span class="gmail_quote">On 1/8/07, <b class="gmail_sendername">Wichert Akkerman</b> <<a href="mailto:wichert@wiggy.net">wichert@wiggy.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Previously Patrick Gerken wrote:<br>> On 1/8/07, Wichert Akkerman <<a href="mailto:wichert@wiggy.net">wichert@wiggy.net</a>> wrote:<br>> >There is large amount of SOAP deployed and all the .NET development<br>
> >suites I'm familiar with make using SOAP really easy, so I expect to see<br>> >SOAP used more rather than less.<br>><br>><br>> As I dont work with .NET, can you outline how integration of soap services
<br>> in a .NET application works, given I have a WSDL file and have to connect to<br>> such a server or provide such a service?<br><br>As long as you use .net tools (like visual studio .net) you point the<br>IDE to a WSDL file and it generates all the glue code for you and you
<br>can call it directly. That also works the other way around: you can add<br>decorators to class methods and it automatically becomes a<br>SOAP-accessible thing with a generated WSDL file (iirc it is generated<br>runtime using introspection).
<br><br>As soon as you have to use SOAP from python you enter a world of pain. A<br>few years ago ZSI was basically unusable. Judging by the traffic on the<br>pywebsvcs list it is a lot better now, but a 2.0 release has been
<br>pending for well over a year now.</blockquote><div><br>Oh, I thought they released it already. But yes they only have release candidates, and the times between different release candidates are still high :-(<br>Yes, this pain thing we realised too.
<br></div></div>