do that uses the template.
Maybe there is some SB annotation trick to declare dependency order among
the beans and whatnot.
But Camel 3 is EOL and we wont have time to investigate old releases.
On Fri, Jun 6, 2025 at 7:44 PM j vh wrote:
> Hello,
> We are upgrading from Camel 3.18.4 to 3.22
Hello,
We are upgrading from Camel 3.18.4 to 3.22.4 to pickup some important bug fixes
but noticed a new problem. When we are instantiating a route in a spring-boot
(2.6.2) app from a route-template the Java builder intermittently fails 3 out
of 4 times. As a workaround we switched to using the
Hello,
Using JMS component to consume messages from a queue with the following example
code using a pollEnrich:
@Override
public void configure() throws Exception {
// Exception handling removed to simplify
from("direct:testRoute")
.routeId("test1-route-id")
.loopDoWhile(body()
Hello,
Using Camel 3.18.0 with Spring-boot 2.6.2 and consuming messages in a route
from an Oracle Advanced queue.
Doing some performance testing consuming JMS messages that showed using a
@JmsListener annotated receiver class and the Camel producer template was
significantly faster than using a
}
}
From: ski n
Sent: June 17, 2022 8:28 AM
To: users@camel.apache.org
Subject: Re: Apache Camel Exception Handling doubt
Hi,
It's good to provide a code example to see what you tried.
Have you also tried to combine it with route configurat
Hello,
btw... I'm using Camel 3.13.0 for this work.
...jvh003
Hello,
I am also trying to use global exception configuration in a Camel route that is
built from a template. The template is created ok and the route created from it
is also ok & working. But the global exception handling is not working as
expected.
Maybe there is another way to customize the
