© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I am going to confirm this since there is a problem. I have been in the situation once before but I could not find out what Windows's SOAP implementation expects. I could however conclude that Ladon's WSDL and SOAP envelope generation is consistent and upholding the SOAP standards. The problem is rather that Microsoft's SOAP client implementation is more or less build to work with the Microsoft SOAP server implementation. SOAP is rather flexible which is a problem in the real world, cause very few clients can live up to this flexibility. gSOAP is one of the best client implementations I know of, and it handles Ladons SOAP implementation just fine. So does Suds for Python and most of the PHP SOAP clients. Suds is the client i have used for testing.
BTW: the soap11 interface in Ladon has namespaces, and that doesn't work with Microsoft either, so I doubt that is the problem.
Just to go into solution mode in your case, I suggest you use JSON-WSP instead, there is a C# client here and that works:
https:/
Best regards Jakob