Yes, use setMessage() on return. I ran into this a while back. Not all
message processes have an in and an out. If the message process doesn't create
an out by using setOut it created a new blank message and you loose everything
from the original message.
-Original Message-
From:
Thanks Claus, fixed it.
Nick
-Original Message-
From: Claus Ibsen
Sent: 07 October 2022 01:00
To: users@camel.apache.org
Subject: Re: Camel 3.14.5 Windows/Linux Type Converter Problems
Hi
Are you by any chance creating an uber-jar/fat-jar of your Camel applications?
If so then mind a
Thanks, that's where I was looking for.
Raymond
On Mon, Oct 10, 2022 at 10:02 PM Nick Bryan wrote:
> I have used a dynamic router (
> https://camel.apache.org/components/3.18.x/eips/dynamicRouter-eip.html)
> for this with rules loaded from a properties file. A check on when the file
> was last
I have used a dynamic router
(https://camel.apache.org/components/3.18.x/eips/dynamicRouter-eip.html) for
this with rules loaded from a properties file. A check on when the file was
last modified told the router to update itself. Each line of the properties
file is your next route e.g.
bar=dir
Consider the following route:
from("direct:a")
.choice()
.when(simple("${header.foo} == 'bar'"))
.to("direct:b")
.when(simple("${header.foo} == 'cheese'"))
.to("direct:c")
.otherwise()
.to("direct:d");
I like to use such choice in a
When you need to set the exchange pattern explicit:
from("direct:foo")
.setExchangePattern(ExchangePattern.InOut)
.to("jms:queue:cheese");
I think when using an async producer template this pattern is automatically
set.
When you want to debug your route, you could set it as:
from(EndPoint
Thanks, Raymond
On the return, I am not using the setOut method but the setMessage as
setOut has been deprecated. It is my understanding that we should use
setMessage instead of setOut.
Stefan
On Mon, 2022-10-10 at 12:43 +0200, ski n wrote:
> To enhance the answer of Claus:
>
> An exchange i
Hi Claus
Thank you for the response.
Background:
We trying to translate between REST and Websockets (io.socket library)
with a custom component in development.
Calling the route:
Exchange exchange = ExchangeBuilder
.anExchange(producerTemplate.getCamelContext())
To enhance the answer of Claus:
An exchange in Camel has two types:
1) InOnly
2) InOut
See: https://camel.apache.org/manual/exchange-pattern.html
With the first type of exchange, "InOnly", the exchange is an event message
(also called 'fire and forget' or 'one-way)'. You will never see the
war
It says that the message did not arrive, and that a timeout was triggered
because of that.
What kind of messaging protocol do you use? JMS, http, etc?
On Mon, Oct 10, 2022 at 12:20 PM Stefan Kok
wrote:
> Hi All
>
> I am having great difficulty making sense of the below log entry:
>
> 10-10-2022
Hi All
I am having great difficulty making sense of the below log entry:
10-10-2022 11:53:11.497 WARN [ForkJoinPool.commonPool-worker-2]
com.experflow.service.OcepService.lambda$changeAgentState$3(OcepService
.java:115) - Exception Message:
org.apache.camel.ExchangeTimedOutException: The OUT mes
11 matches
Mail list logo
