...
It is the responsibility of the code within messaging endpoint to retrieve that command or data, transform it into a message, and then send it on to a particular messaging channel. Then, the receiving endpoint will retrieve the message, extract its contents, and pass it to the application in a meaningful way.
Types of endpoint
Apache Camel defines two basic types of endpoint:
Consumer endpoint — This type will appears at the start of a route and will read In messages from an incoming channel (equivalent to a receiver endpoint).
Producer endpoint — This type will appear at the end of a route and writes In messages to an outgoing channel (equivalent to a sender endpoint). It is possible to define a route with multiple producer endpoints.
Endpoint URIs
An endpoint is represented by an endpoint URI, which typically encapsulates the following kinds of data:
...
NOTE: componentPrefix is a URI prefix that will identify a particular Apache Camel type (jms, file, HTTP, etc), the remaining part of the URI (componentSpecificURI), has a syntax defined by the particular component.
Consumer Endpoint
To define a route that connects the consumer endpoint of file://local/router/messages/foo directly to the producer endpoint of jms:Foo.Bar, we would use the following:
...