I'd like to see some examples of interoperability issues with RPC encoding web service.
Some mentioned soapEnc:string vs. xsd:string. In other words, one SOAP toolkit may use XML schema's string type, but another toolkit may use SOAP Encoding string type and therefore two different types on the same string.
This sounds like a real big issue, that means, as long as we use string in WSDL, we have to tell our web service consumer to use or not to use certain SOAP toolkit to generate client stubs, otherwise, they run into this problem.
Can someone give other examples, and what is the root cause of these interoperability issues? I read some concepts, but it'd be best to see concrete examples and how Document/Literal would fix them.
Joined: Aug 19, 2005
Originally posted by Yan Zhou: what is the root cause of these interoperability issues?[/QB]
Ultimately, section 5 of the SOAP specification was open to some diverging interpretations. 5. SOAP Encoding
Originally posted by Yan Zhou: but it'd be best to see concrete examples and how Document/Literal would fix them.[/QB]
Ultimately adoption of RPC/literal or Document/literal as outlined by the WSI Basic Profile (which disallows certain features of SOAP and WSDL and resolves the ambiguities) fixes these problems.