Uses of Package
org.apache.camel.impl.engine

Packages that use org.apache.camel.impl.engine

Package	Description
org.apache.camel.impl.engine

Classes in org.apache.camel.impl.engine used by org.apache.camel.impl.engine

Class	Description
AbstractCamelContext	Represents the context used to configure routes and the policies to use.
AbstractDynamicRegistry	Base implementation for EndpointRegistry, TransformerRegistry, and ValidatorRegistry.
BaseExecutorServiceManager	Base ExecutorServiceManager which can be used for implementations
CamelInternalProcessor	Internal Processor that Camel routing engine used during routing for cross cutting functionality such as: Execute UnitOfWork Keeping track which route currently is being routed Execute RoutePolicy Gather JMX performance statics Tracing Debugging Message History Stream Caching Transformer ... and more.
CamelPostProcessorHelper	A helper class for Camel based injector or bean post-processing hooks.
DefaultConfigurerResolver	Default configurer resolver that looks for configurer factories in META-INF/services/org/apache/camel/configurer/.
DefaultFactoryFinder	Default factory finder.
DefaultFactoryFinder.ClassSupplier
DefaultProducerTemplate	Template (named like Spring's TransactionTemplate invalid input: '&' JmsTemplate et al) for working with Camel and sending Message instances in an Exchange to an Endpoint.
DefaultRouteController	A default RouteController that starts the routes in a fail-fast mode, which means if any of the routes fail to startup then this causes Camel to fail to startup as well.
DefaultUnitOfWork	The default implementation of UnitOfWork
DurationRoutePolicy.Action
PrototypeExchangeFactory	ExchangeFactory that creates a new Exchange instance.
PrototypeProcessorExchangeFactory	ProcessorExchangeFactory that creates a new Exchange instance.
RouteService	Represents the runtime objects for a given route so that it can be stopped independently of other routes
SubscribeMethodProcessor	A Processor which is used for POJO @Consume where you can have multiple @Consume on the same endpoint/consumer and via predicate's can filter and call different methods.