In the first installment of this series, we discussed the need for integration, and some of the potential pitfalls, especially when attempting to roll your own integration system. We then proceeded to discuss some of the patterns in Gregor Hohpe's and Bobby Woolf's aptly named "Enterprise Integration Patterns" and their corresponding implementations in Spring Integration. We discussed the core patterns that make up the founding blocks of Spring Integration - "Message Channel", "Message" and "Message Endpoint". In this article we will explore a few more patterns that will allow you to route, filter and manipulate messages as well as talk to external systems. We will learn how to do this while leveraging Spring's declarative model that lets you focus on your domain, and let Spring Integration handle the specifics of messaging.
Raju Gandhi is a Java/Ruby/Clojure developer and a programming language geek. He has been writing software for well over a decade in several industries including education, finance, construction, manufacturing and retail sectors. Raju has a graduate degree in Industrial Engineering from Ohio University. In his spare time you will find Raju reading, or watching movies, or playing with yet another programming language. He is affectionately known as looselytyped on Twitter.