Camel in Action

List of Figures

Chapter 1. Meeting Camel

Figure 1.1. Camel DSLs use real programming languages like Java, so you can use existing tooling support.

Figure 1.2. Files are routed from the data/inbox directory to the data/outbox directory.

Figure 1.3. Messages are entities used to send data from one system to another.

Figure 1.4. A message can contain headers, attachments, and a body.

Figure 1.5. A Camel exchange has an ID, MEP, exception, and properties. It also has an in message to store the incoming message and an out message to store the result.

Figure 1.6. At a high level, Camel is composed of processors, components, and routes. All of these are contained within the CamelContext.

Figure 1.7. The CamelContext provides access to many useful services, ...