Does anybody have the same issue? I used to use mule and the Qpid connection
can be retried unlimited until Qpid is up running. Somehow I didn't receive
exception in Camel if Qpid is down.
Regards,
Welly
From: Welly Hong
Sent: Friday, May 24, 2019 3:49 PM
To: users@camel.apache.org
Subject:
Hi
Ah yeah that is correct. So you can help by creating a PR with the
commit I did on master to implement this for the camel-2.x branch.
Mind that master and camel-2.x branches has drifted due the big work
on Camel 3. So we dont have much time ourselves to maintain 2.x. So
community have to step
Sorry I missed the first reply.
I am using camel 2.0.24 but it doesn't work what you are suggesting e.g)
.setHeader("claimCheckKey", simple("${headers.CamelFileName}"))
.claimCheck(ClaimCheckOperation.Set, "claimCheckKey", "body")
I've debugged the DefaultClaimCheckRepository and the literal
Hi
I replied previously about how you can set the key in another header first
On Thu, May 30, 2019 at 11:22 AM erars+jonathan.cook
wrote:
>
> Many thanks Claus. I saw you already fixed it ;-) I was going to have a
> go..
>
> Do you have any suggestion for a quick work around? Could I override
Many thanks Claus. I saw you already fixed it ;-) I was going to have a
go..
Do you have any suggestion for a quick work around? Could I override
the claim check processor in my own processor or better to do something
like in the ClaimCheckTest using beans..
Hi,
I am trying to call Apaches' StringUtils class from my spring XML route file.
I got to with the following code.
In Camel 2.x, you can set the key in a header first via
setHeader("myKey", simple("..."))
And then use myKey as the key.
On Thu, May 30, 2019 at 9:44 AM Claus Ibsen wrote:
>
> Hi
>
> This is currently not supported, the key is static at the moment. I
> have logged a ticket to allow to use
Hi
This is currently not supported, the key is static at the moment. I
have logged a ticket to allow to use simple language in the key
https://issues.apache.org/jira/browse/CAMEL-13599
On Wed, May 29, 2019 at 11:29 PM erars+jonathan.cook
wrote:
>
> I got rid of the ManagedClaimCheck exception
