Find Unimplemented Operations Using a SOAP Fault

Exercise the OrderTshirt operation in SoapUI against a deployed APIkit for SOAP project before that operation is implemented. The runtime returns a SOAP fault that names the missing router operation so you know which flow to build in Anypoint Studio. This example requests a large t-shirt for a customer named John, which the stub cannot process yet.

In SoapUI, create a new SOAP project and put the URL for your deployed Mule APIkit project in the initial WSDL file.
In this example, the URL is http://localhost:8081/TshirtService/TshirtServicePort?wsdl.
In SoapUI, request a large t-shirt for John by entering some values into the request envelope:
1. Select Projects > TshirtServicePort?wsdl > TshirtServiceSoapBinding > OrderTshirt > Request 1.
2. Enter L between the <size> tags.
3. Enter John between the <name> tags.

Submit the request.

The result is the SOAP fault:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault xmlns:soap="http://schemas.xmlsoap.org/soap/envelope">
         <faultcode>soap:Server</faultcode>
         <faultstring>Operation [OrderTshirt:\soapkit-config] not implemented</faultstring>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

Find Unimplemented Operations Using a SOAP Fault

See Also