Summary
In this chapter, we have seen how to use beans in Camel routes.
First, we saw the different registries supported, where Camel looks for beans. Specifically, we saw the mapping between the Camel DSL used and the default registry loaded. We saw examples of different registries in action, including the composite registry. For this lookup, Camel acts as a service activator. The example showed how to leverage the Spring or Blueprint service registry.
We also saw the usage of the annotations to qualify the method and arguments binding. Those annotations can be combined with language annotations, allowing a very powerful way to populate method arguments.
In the next chapter, we will see one of the Camel key features—routing and Enterprise Integration Patterns support. We will see ready-to-use processors and DSL implementing different EIPs.
