[Soap-Python] Interoperability problem between soaplib and MS .Net 3.5 SOAP
burak.arslan at arskom.com.tr
Tue Apr 13 23:13:11 CEST 2010
On 04/13/10 23:35, Christian Hudon wrote:
> On Apr 11, 6:11 pm, Burak Arslan<burak.ars... at arskom.com.tr> wrote:
>> this has been a known issue for some time now. the fix will break
>> backwards compatibility, so unless there's a strong community consensus
>> on changing this, i think it should stay as it is.
> Hm. I don't know how you were planning on gauging community consensus,
> but my feel is that for people who are new to soaplib and want to
> interoperate with other SOAP implementations (of which Microsoft's is
> the most widespread), this problem is rather a deal-breaker. It's also
> a deal-breaker if you're writing a SOAP server that implements an
> existing interface and have no control over the format of the RPC
> calls made by the client. Personally, if soaplib can't interoperate
> correctly with Microsoft's SOAP stack, I'll have to use something
I have to agree, except that there's no major interop problem. (the
response can reportedly be parsed by .net) You just need to go one level
deeper than you'd expect to reach it.
Once someone patches this, we'll see how it goes.
> I understand that just changing the existing behavior without
> transition and breaking existing users is not an option. But it
> doesn't make the bug into a feature, especially for people wanting to
> use SOAP to interoperate with other systems..
I was not trying to imply that this behavior is not a bug. It's just
that its fix would break existing code which had to work around, so
should not go into an official release silently.
Just changing it may be an option. I could speculate, but as I said, we
first need a patch.
> Also, is there a patch or git branch that has that fix, so I can test
To my knowledge, no.
More information about the Soap