THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Class resolvers
- Lifecycle factories
- Registry for lookup
- Debugger, Tracer and Delay
- Intercept
- Graceful Shutdown
Camel will configure these functions by doing a lookup in the Spring bean registry to find beans of the given type
When Camel finds and uses any of these it logs at INFO level.
...
Type | Number of beans | Description |
|---|---|---|
PackageScanClassResolver | 0..1 | To use a 3rd party package scan resolver. More details at Pluggable Class Resolvers. |
ClassResolver | 0..1 | To use a 3rd party class resolver. More details at Pluggable Class Resolvers. |
FactoryFinderResolver | 0..1 | To use a 3rd party factory finder. |
Registry | 0..1 | To use a 3rd party bean registry. By default Camel will use Spring ApplicationContext as registry. |
Debugger | 0..1 | To use a Debugger usually for tooling. |
Tracer | 0..1 | To use a 3rd party Tracer. |
TraceFormatter | 0..1 | To use a bean that has the tracing options configured. |
HandleFault | 0..1 | To use a 3rd part fault handler to handle FAULT messages. |
Delayer | 0..1 | To use a 3rd part Delayer. |
ManagementStrategy | 0..1 | Camel 2.1: To use a 3rd part strategy for management, for example JMX management. |
EventFactory | 0..1 | Camel 2.1: To use a 3rd part event factory. |
EventNotifier | 0..1 | Camel 2.1: To use a 3rd part event notifier. |
InflightRepository | 0..1 | Camel 2.1: To use a 3rd part inflight repository. |
ShutdownStrategy | 0..1 | Camel 2.2: To use a 3rd part shutdown strategy. |
And the following options have support for any number of beans defined.
...