Developing Services with Apache Camel - Part II: Creating and Testing Routes
This article is the second in a series on Apache Camel and how I used it to replace IBM Message Broker for a client.
The first article,
Developing Services with Apache Camel - Part I: The Inspiration, describes why I chose Camel for this project.
To make sure these new services correctly replaced existing services, a 3-step approach was used:
- Write an integration test pointing to the old service.
- Write the implementation and a unit test to prove it works.
- Write an integration test pointing to the new service.
I chose to start by replacing the simplest service first. It was a SOAP Service that talked to a database to retrieve a value based on an input parameter. To learn more about Camel and how it works, I started by looking at the CXF Tomcat Example. I learned that Camel is used to provide routing of requests. Using its CXF component, it can easily produce SOAP web service endpoints. An end point is simply an interface, and Camel takes care of producing the implementation.
[Read More]