We use ZSI here for both SOAP clients and servers and we've
successfully talked to .Net clients and SOAPui. As explained by the
ZSI webpage, SOAP.py is essentially deprecated and is being merged
into ZSI.
A word of warning -- SOAP (with ZSI or otherwise) is probably not
going to be easy and you'll have to test with every SOAP library you
want to be able to communicate with. You'll want to provide WSDL and
Disco files from the outset [1] and keep an eye out for differences in
support for authentication and other optional features.
[1] ZSI can funciton without them (by accepting any valid SOAP
response and converting it to an object) but this isn't supported by
the .Net implementation (for example).
This is important. Some SOAP clients and servers are unhappy with each
other (placement of namespaces was what bit us) and can cause lots of
pain and frustration.
--J
For those of use forced to use SOAP from Python, a new option has
emerged -- soaplib. I haven't had a look at the code yet, but the
creation of SOAP services and clients looks really nifty (@soapmethod
decorator for specifying SOAP methods, build-in WSGI App for the SOAP
server, ability to hook into SOAP calls for testing and logging). And
it can generate WSDL files (and seems to do so automatically behind
the scenes by default).
http://trac.optio.webfactional.com/wiki/soaplib
Schiavo
Simon