[Soap-Python] Interoperability problem between soaplib and MS .Net 3.5 SOAP

[Jamie Kirkpatrick]

Does someone want to work a patch up on a branch and issue a pull request?
 Does this need to be a switchable feature somehow so as not to break
interop on existing systems?

Ta

-- 
Jamie Kirkpatrick
07818 422311
On 14 April 2010 05:13, Burak Arslan <burak.arslan at arskom.com.tr> wrote:

> 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
>> else.
>>
>>
>>
>
> Hi Christian,
>
> 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
>> it?
>>
>>
>>
>
> To my knowledge, no.
>
> best,
>
> burak
>
> _______________________________________________
> Soap mailing list
> Soap at python.org
> http://mail.python.org/mailman/listinfo/soap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/soap/attachments/20100419/846d716c/attachment.html>