Registry

It's possible to use a bean exactly as a processor, meaning, directly inline in a route. This allows us to use a lightweight, simple programming model, reusing existing components in Camel routes.

When a bean is used in a Camel route, the bean must be registered in a registry. Depending on which environment is running, Camel bootstraps different registries. When Camel works with beans, it looks them up in the registry to locate them.

The registry is defined at the CamelContext level. A registry is automatically created for you by Camel with the CamelContext. If you create the CamelContext manually, you can instantiate a registry and put this registry in the CamelContext.

The following registry implementations are shipped with Camel:

• SimpleRegistry
• JndiRegistry
• ApplicationContextRegistry
• OsgiServiceRegistry

Let's have a look at each one of these in detail.

SimpleRegistry

SimpleRegistry is a simple implementation, mostly used for testing where only a limited number of JDK classes...