-
Notifications
You must be signed in to change notification settings - Fork 0
Camel
- Blog discussing the use of aggregator
Camel is composed of:
- processors
- components
- routes
All these are contained within the CamelContext
One of the services that CamelContext provides is Registry which allows you to look up beans. Default will be a JNDI registry but using Camel from Spring, this will be the Spring ApplicationContext.
Can the registry be based on Guice?
Each route in Camel has a unique identifier (used for logging, debugging, monitoring and starting and stopping routes). Routes have exactly one input source for messages, effectively tied to an input endpoint.
Handle things in between endpoints like
- EIPs
- Routing
- Transformation
- Mediation
- Enrichment
- Validation
- Interception
Associated with a name that's used in a URI and they act as a factory of endpoints.
E.g. a FileComponent is referred to by file in a URI, and it creates FileEndpoints.
An endpoint is the Camel abstraction that models the end of a channel through which a system can send or receive messages.
In Camel, you configure endpoints using URIs, such as file:data/inbox?delay=5000, and also refer to endpoints the same way.