SOAP WSDLs - RPC/Literal

Example of the SOAP message


Here are the strengths and weaknesses of this approach:


  1. The WSDL is still about as straightforward as it is possible for WSDL to be.
  2. The operation name still appears in the message.
  3. The type encoding info is eliminated.
  4. RPC/literal is WS-I compliant.


  1. You still cannot easily validate this message since only the <x …>5</x> and <y …>5.0</y> lines contain things defined in a schema; the rest of the soap:body contents comes from WSDL definitions.
developer/rpc_literal.txt · Last modified: 2011/03/02 13:37 by irina

Page Tools