Request-Reply Message Exchange Patterns
In a request-reply interaction, the Mediator is invoked and sends a reply to the caller. Depending on the type of routing rule target, the responses, faults, and callbacks are handled as shown in Table 24-3:
Table 24-3 Response When Mediator's WSDL Is a Request Reply
| Routing Rule Target Type | Response |
|---|---|
|
Request |
There is no response from the target, but there should be at least one sequential routing rule with a request-response service. |
|
Request Response |
The response is sent back to the caller. The response can be forwarded to another target or event, but there should be at least one sequential routing rule that returns a response back to the caller. |
|
Request Response Fault |
The response is sent back to the caller. The fault is forwarded to another target or event. |
|
Request Callback |
There is no response from the target, but there should be at least one sequential routing rule with a request-response service. The callback is forwarded to another target or event. |
|
Request Response Callback |
The response is sent back to the caller. The callback is forwarded to another target or event. |
|
Request Response Fault Callback |
The response is sent back to the caller. The callback and fault are forwarded to another target or event. |
Figure 24-2 illustrates the request-reply message exchange pattern.
Figure 24-2 Request-Reply Message Exchange Pattern
Description of "Figure 24-2 Request-Reply Message Exchange Pattern"