We can consider for some HTTP components that support dynamic parts of their endpoints from Camel headers such as HTTP_QUERY and others.
We can then in toD detect those components and then build a processor chain that does
- setHeader - set dynamic header HTTP_QUERY
- toD - call the endpoint with a more static uri
This optimises to reuse the toD with more static uris, especially if you hit the same host for each toD and its only the query parameters that are dynamic.
Today developers would need to use setHeader and to combo to do this, instead of a single toD.
The trick is to separate the query parameters and the endpoint parameters and only set query parameters in the setHeader, and the endpoint parameters in toD.