Chapter 4. Beans
In the previous chapter, we saw one of the key, and very helpful, Camel components—the processor. However, a processor is tied to Camel as it extends the org.apache.camel.Processor interface.
This means that in order to reuse some existing beans in your application, you have to wrap it in a processor, meaning additional code to be maintained.
Fortunately, Camel has extensive support for POJO and beans, and bean model frameworks such as Spring or Blueprint.
In this chapter, we will see:
- How Camel looks for beans in different registries and the different registry implementations
- How Camel acts as a service activator to load the beans and bind the parameters
- The Camel annotations that enables advanced binding
- The Camel language annotations ...
Get Mastering Apache Camel now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
