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
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 that allow the usage of code in parameter binding