When using the DSL to create Routes you typically refer to Message Endpoints by their URIs rather than directly using the Endpoint interface. Its then a responsibility of the CamelContext to create and activate the necessary Endpoint instances using the available Component implementations.
Using the Fluent Builders
Using the Spring XML Extensions
Available as of Camel 2.16
There is a new <toD> that allows to send a message to a dynamic computed Endpoint using one or more Expression that are concat together. By default the Simple language is used to compute the endpoint. For example to send a message to a endpoint defined by a header you can do
And in Java DSL
You can also prefix the uri with a value because by default the uri is evaluated using the Simple language
And in Java DSL
In the example above we compute an endpoint that has prefix "mock:" and then the header foo is appended. So for example if the header foo has value order, then the endpoint is computed as "mock:order".
This is done by specifying the name of the language followed by a colon.
You can also concat multiple Language(s) together using the plus sign
+ such as shown below:
In the example above the uri is a combination of Simple language and XPath where the first part is simple (simple is default language). And then the plus sign separate to another language, where we specify the language name followed by a colon
You can concat as many languages as you want, just separate them with the plus sign
The Dynamic To has a few options you can configure
|uri||Mandatory: The uri to use. See above|
|pattern||To set a specific Exchange Pattern to use when sending to the endpoint. The original MEP is restored afterwards.|
|cacheSize||Allows to configure the cache size for the |
|ignoreInvalidEndpoint||Whether to ignore an endpoint URI that could not be resolved. If disabled, Camel will throw an exception identifying the invalid endpoint URI.|
For more details see
Using This Pattern
If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.