| Gliffy Diagram |
|---|
| size | L |
|---|
| name | Message flow in Route |
|---|
| align | left |
|---|
| version | 2 |
|---|
|
Messsage exchange patterns and the Exchange object
...
The Exchange API provides two methods to get a message, either getIn or getOut.
Obviously the getIn gets the IN message, and the getOut gets the OUT message.
Flow of an exchange through a route
| Gliffy Diagram |
|---|
| size | L |
|---|
| name | Message flow in Route |
|---|
| align | left |
|---|
| version | 2 |
|---|
|
- The out message from each step is used as the in message for th next step
- if there is no out message then the in message is used instead
- For the InOut MEP the out from the last step in the route is returned to the producer. In case of InOnly the last out is thrown away
| Tip |
|---|
| title | Beware of getOut to check if there is an out message |
|---|
|
exchange.getOut creates an out message if there is none. So if you want to check if there is an out message then you should use exchange.hasOut instead |
Using getIn or getOut methods on Exchange
...
