Request and Response - Get Exchange Rate

WSDL Tutorials - Herong's Tutorial Examples

∟WSDL 1.1 and SOAP 1.1 Examples - Document and RPC Styles

∟Request and Response - Get Exchange Rate

This section provides a mock request and a mock response for the Get Exchange Rate Web service that uses SOAP 1.1 over HTTP with rpc/encoded as the message style and the encoding option.

Here is a mock request generated with SoapUI with some data entered by myself for GetExchangeRate_WSDL_11_SOAP_11_RPC.wsdl:

<soapenv:Envelope
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:ser="https://www.herongyang.com/Service/">
  <soapenv:Header/>
  <soapenv:Body>
    <ser:GetExchangeRate
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      <fromCurrencyPart xsi:type="xsd:string">USD</fromCurrencyPart>
      <toCurrencyPart xsi:type="xsd:string">JPY</toCurrencyPart>
      <datePart xsi:type="xsd:date">2018-08-08</datePart>
    </ser:GetExchangeRate>
  </soapenv:Body>
</soapenv:Envelope>

Notice that:

SoapUI uses the operation name "GetExchangeRate" as the top level element in the SOAP Body, because style="rpc" is specified in the WSDL document. The target namespace: https://www.herongyang.com/Service/ is used to prefix "GetExchangeRate".
SoapUI uses the message part names defined in the WSDL document as sub element names representing input parameters to the RPC function. This should be fine for the server, because the RPC is reading parameters by positions. Parameter names do not matter.
SoapUI inserts parameters in the order specified in parts="fromCurrencyPart toCurrencyPart datePart". This is an expected good behavior.
SoapUI inserts xsi:type="xsd:..." in each parameter, because use="encoded" is specified in the WSDL document.
SoapUI also adds the default encoding style soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" because of use="encoded".

Here is a mock response generated with SoapUI 3.0.1 with some data entered by myself:

<soapenv:Envelope
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:ser="https://www.herongyang.com/Service/">
  <soapenv:Header/>
  <soapenv:Body>
    <ser:GetExchangeRateResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      <ratePart xsi:type="xsd:decimal">123.14</ratePart>
    </ser:GetExchangeRateResponse>
  </soapenv:Body>
</soapenv:Envelope>

Notice that:

SoapUI uses the operation name "GetExchangeRate" and the word "Response" to make the top level element name, GetExchangeRateResponse, in the SOAP Body, because style="rpc" is specified in the WSDL document. The target namespace: https://www.herongyang.com/Service/ is used to prefix "GetExchangeRateResponse".

Conclusion, for RPC method based Web service, the request SOAP Body element will be named as the operation name; and the response SOAP Body element will be named as the operation name plus "Response".