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, the most notable being components, type converters, a registry, endpoints, routes, data formats, and languages.
Figure 1.8. An endpoint acts as a neutral interface allowing systems to integrate.
Figure 1.9. Endpoint URIs are divided into three parts: a scheme, a context path, and options.
Figure 1.10. How endpoints work with producers, consumers, and an exchange
Figure 1.11. An event-driven consumer waits idle until a message arrives, at which point it wakes up and consumes the message.
Figure 1.12. A polling consumer actively checks for new messages.
Chapter 2. Routing with Camel
Figure 2.1. A message router consumes messages from an input channel and, depending on a set of conditions, sends the message to one of a set of output channels.