- Web Services Testing with soapUI
- Charitha Kankanamge
- 186字
- 2021-08-05 18:39:23
Message exchanging patterns
As we have already discussed, the web services communicate with each other and the other programs by sending messages. If we consider two SOAP processing nodes, the communication pattern between the two entities can be defined as a message exchanging pattern (MEP). The primary message exchanging patterns are:
- Request-response
- Fire and forget
In a request-response pattern, when a source entity (service requester) transmits a message to a destination (service provider), the provider should respond to the requester. This is the most commonly used message exchanging pattern and we will use this in most of the examples in this book.
In the following diagram, a service requester sends a SOAP request message to a service provider:

Upon receiving the SOAP request message, the service provider responds with a SOAP response as shown in the following diagram:

When a response to a request message is not expected from a web service (or service provider), it is known as a fire and forget message exchange pattern. For example, if we send a ping request to a web service, we do not expect a response message back.
- 企業數字化創新引擎:企業級PaaS平臺HZERO
- MongoDB管理與開發精要
- 業務數據分析:五招破解業務難題
- 大數據算法
- 大數據:從概念到運營
- SQL優化最佳實踐:構建高效率Oracle數據庫的方法與技巧
- SQL Server 2012數據庫管理教程
- R Object-oriented Programming
- Web Services Testing with soapUI
- 中文版Access 2007實例與操作
- The Natural Language Processing Workshop
- Filecoin原理與實現
- 信息融合中估計算法的性能評估
- 數據之美:一本書學會可視化設計
- 數據庫原理及應用實驗:基于GaussDB的實現方法