Show description

This is done for each piece of luggage. An existing Java service—the BoardingCard service— knows how to interact with the scale. 50 Mule 2: A Developer’s Guide to ESB and Integration Platform These luggage details are collected by the check-in software and returned to the counter’s onboard electronics; the appropriate luggage tags are then printed. It is the check-in staff’s responsibility to manually affix these tags to the luggage. Receipts are given to the passenger so they can claim the luggage at their destination.

These messages are typically “lost,” or “dropped,” by the router and not handled at all. It is worth looking into the reason for dropped messages though, since such 38 Mule 2: A Developer’s Guide to ESB and Integration Platform messages could be of significant value—perhaps they imply some sort of error or require additional processing before they can be successfully handled by this service. In Mule these messages can be caught and handled in one of three ways: the message can be logged, forwarded to a third-party endpoint, or have some sort of customized behavior applied to it.

It allows you to synchronously send a message along an endpoint and direct the response to another endpoint without performing any interim processing on the result. You can list any number of endpoints and the message flow will use them sequentially, in the order they are declared. This is useful for situations where you have a request-response scenario (such as a web service) whose result needs to be directed to another endpoint, for example a JMS queue. Note that if the message flow is asynchronous, the chaining router will enforce synchronicity on all further message flows until it gets to the last endpoint in its list.