Chapter 8. Implementing enterprise-quality message flows
In this chapter:
- Understanding error handling
- Using the Acegi framework
- Implementing an Apache LDAP server
- Using JAAS to secure ServiceMix
- Implementing transaction handling
Implementing message flows involves functionality such as routing, transformation, and connectivity. However, that’s not enough to implement enterprise integration solutions in real-life integration projects. You also need to be able to deal with, for example, error handling, security, and transactions. In this chapter, you’ll learn all the details.
Because message flows won’t run as expected all the time, we start this chapter with a discussion on error handling. It is essential (for the implementation of security and transactions as well) to be able to handle errors on all parts of a message flow. Because integration solutions typically deal with numerous messages, addressing errors is often difficult. A common solution is to send messages to error queues or “dead letter” queues, where ESB administrators can be alerted when an error occurs. You’ll see that implementing error-handling functionality is quite easy with Mule and ServiceMix.