Perfect - thank you!!!
> -Original Message-
> From: Claus Ibsen
> Sent: Thursday, June 27, 2019 1:00 PM
> To: users@camel.apache.org
> Subject: Re: How to use simple expression in properties file?
>
> Hi
>
> Yeah use $simple{header.xxx}
>
> On Thu, Jun 27, 2019 at 4:55 PM Steve Huston
Hi
Yeah use $simple{header.xxx}
On Thu, Jun 27, 2019 at 4:55 PM Steve Huston wrote:
>
> Thank you for clarifying that the string for toD is already a simple string.
> However, it still fails with the same exception at runtime:
>
> Caused by: java.lang.IllegalArgumentException: Could not
Hi Stig,
Endpoint options are set at a later stage[1] which is why you don't see the
desired cutstom client.
You could also set a breakpoint at [2] to see which client is really used
for the update method. From what I see you're setting it up correctly.
HTH,
John.
[1]
Thank you for clarifying that the string for toD is already a simple string.
However, it still fails with the same exception at runtime:
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder
'header.SMID' in value "file://.?fileName=status-${header.SMID}.txt"
-Steve
>
Hi
We also discussed Camel and transactions within Red Hat with some
customers recently. And Duane Hawkins wrote this nice piece of
response which I am allow to share here in the public with his
permissions
There are a couple of possible gotchas here:
1. It is important to note that Camel
Hi John,
I work with Paw. We're trying to set either the client or client factory via
the URI header, because we'd like to add a request interceptor to the client.
We would like to log error response bodies.
You are right that it was weird to use HTTP_QUERY. Instead we've done the
following:
Hi,
I would like to use different RouteBuilders to declare my routes. I have a
RouteBuilder that sets up some REST endpoints, and forwards requests to routes
declared in other RouteBuilders. The REST RouteBuilder sets up some general
exception handling to return "nice" HTTP status codes in
