...
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. In Camel 2.2 onwards you can have multiple notifiers, see next table. |
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. |
...
Type | Number of beans | Description |
---|---|---|
InterceptStrategy | 0..n | To use your own Intercept that intercepts every processing steps in all routes in the CamelContext. For instance you can use this to do an AOP like performance timer interceptor. |
LifecycleStrategy | 0..n | Camel 2.1: To use 3rd party lifecycle strategies. By default Camel uses a JMX aware that does JMX instrumentation. |
EventNotifier | 0..n | Camel 2.2: To use 3rd part event notifiers. |
Camel will log at INFO
level if it pickup and uses a custom bean using org.apache.camel.spring.CamelContextFactoryBean
as name.
...