Clashing Spring placeholders with Camel "simple" language

Today I tried to build a dynamic endpoint URL for one of my camel routes. I am using the Spring properties bridge to load configuration parameters and I try to build the endpoint URL using my configuration and request headers.

This is what my recipientList looks like:


The important part is the $simple{in.header.accessToken}. First I was using the usual Camel syntax ${in.header.accessToken}, but always got an exception on startup stating

Could not resolve placeholder 'in.header.myHeader' in string value "restlet:MYBASEURL?parameter=${in.header.myHeader}"

The solution is to make the use of the simple language explicit like in $simple{in.header.myHeader}.

Weitere Artikel

Nach den Crossfit Open

Crossfit Open WOD 17.5

Crossfit Open WOD 17.4

Crossfit Open WOD 17.3

Crossfit Open Workout 17.2

Crossfit Open Workout 17.1

Run Feedbin in your local Kubernetes cluster

Running Threema Web in Docker

Neues Workout Video

Diät Update #1