Mike McGurrin wrote:
>  
> ...
>  
>  Also, it fails with many of the Microsoft .Net servers.  My guess is
>  because they reference the 2001 schema version in the namespace
>  definitions, and the client uses 1999 and declares an error when it sees
>  2001.  I've since learned from the developer of Soapy (Adam Elman) that
>  someone had sent him a patch (not posted on SourceForge at this time) to
>  address this:

That was my patch so it should be in ActiveState's version.

> ...
>  Is the Python implementation at ActiveState undergoing active
>  development?  The description says it's based on Soapy, which is no
>  longer under active development by the author.  Is there active work on
>  a Python wsdl-aware client, either ActiveState's reference
>  implementation or others?  What about server side with Python?  Thanks!

The soapy developer has offered me CVS access so that I could take the
code forward. Unfortunately I got distracted by a few conferences and
then the other responsibilities that pile up when you are at them.

Right now I'm pretty confident that ZSI is the most actively maintained
SOAP library for Python. It is unfortunate that the names "soap.py",
"SOAP.py" and "soaplib.py" are already taken because it may well be the
"standard" Python SOAP library in the long run.

The question is which half-finished WSDL library to merge with ZSI.
SOAP.py has one. There is wsdl4py and ActiveState has a one. None handle
all of the details of complex types and neither does any Perl library.
It is an incredibly, er, complex issue that is somewhat daunting. 

 Paul Prescod
_______________________________________________
Ws-dev mailing list
Ws-dev@[...].com
http://listserv.ActiveState.com/mailman/listinfo/ws-dev