4 ms·

.NET WCF to another WCF integration is fine, but if you try and hook a .NET SOAP webservice to one written in Java, and you'll have pulled all of your hair out

by junto 11y ago

.NET WCF to another WCF integration is fine, but if you try and hook a .NET SOAP webservice to one written in Java, and you'll have pulled all of your hair out after two weeks. The reverse is just the same. They all have slightly different implementations of the specifications. Make that one week if you have to start dealing with the monster that is called WS-* a.k.a. WS-WTF. I wrote an article on this many moons ago. It is still one of my most frequently read posts: https://benpowell.org/supporting-the-ws-i-basic-profile-password-digest-in-a-wcf-client-proxy/ https://benpowell.org/supporting-the-ws-i-basic-profile-pass... It just goes to show how many SOAP integrations are still going on in the "enterprise".

deleted 11y ago
[deleted]
mohaine 11y ago
This. WCF is SO broken but you don't notice if you use it on both sides. It has been a few years but it used to require your soap attributes to be in predefined order and would break otherwise. so if it expected: <object> <a>A</a> <b>B</b> <c>C</c> </object> And you sent in: <object> <b>B</b> <c>C</c> <a>A</a> </object> The parsed object was: {"a":null,"b":"B","c":"C"} Java Soap libs normally creates the request by reflection and attribute order depends on the exact JVM and compiler implementation and combination. This one took way to long to figure out.