Within the Bridge, it is important to differentiate between the following scenarios:

• a SOAP call via an adapter within a service (see SOAP Adapter)
• the called SOAP service itself

In this section you will find information on the called SOAP service itself.

The Bridge supports SOAP 1.1. as well as SOAP 1.2, whereas SOAP 1.2 is only supported for document-literal encoded services. Which version to use for your web service is your choice. However, be aware of the fact that using document-literal encoded operations you will have to directly edit the SOAP request in test cases of the SOAP Test Tool and the E2E Analyzer to provide input parameters.

The procedure described in  Working with the SOAP Test Tool and Inserting Test Data only applies to RPC encoded operations.Find more information on SOAP encoding styles on SOAP Service.

SOAP messages are mapped to UML classes as described on XML - UML Class Mapping.

SOAP Service and HTTP SupportXML - UML Class Mapping

X-Transaction-ID corresponds to SOAP header TransactionID, and X-Request-ID corresponds to SOAP header CorrelationID. The SOAP header overrules the HTTP header if set.

Additionally, any client calling an xUML SOAP service can specify the following HTTP header: X-Bridge: NoErrorReturn
This header will change the HTTP status code in case of error:

• SOAP call without error
  No change, HTTP status code 200 (as expected).

• SOAP call with error
  HTTP status code 200 (instead of 500).

  Info
  icon false
  The response body does not change in this case and will still report the error details.