Page History
| Div | ||
|---|---|---|
| ||
|
Within the E2E Bridge, it is important to differentiate between the following scenarios:
...
In this section you will find information on the called SOAP service itself.
| Noteinfo | ||
|---|---|---|
| ||
The Bridge supports SOAP version 1.1. Added in Builder 5.1.8.56 and Runtime 5.1.82.1 Support of SOAP version 1.2 for document-literal encoded services. |
The E2E 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.
...
| icon | false |
|---|
...
Find more information on SOAP encoding styles on SOAP Service.
SOAP Service and HTTP Support
Refer to HTTP Protocol Support regarding general information on HTTP protocol support in this context.
...
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.
Overview
Content Tools