The Camel community announces the immediate availability of Apache
Camel K 1.4.0.
This is a major release containing new features and improvement for
stability. You can find more information in the release notes[1].
The artifacts are published and ready for you to download either
from the Apache
Hello
I have Camel routes that look like this:
Processor1->Processor2->Processor3->Processor4
Processor1 does some business logic.
Processor2 puts a message on Google PubSub.
Processor3 takes the message from Google PubSub.
Processor4 uses info from the message to do things.
My problem is that
Is the Process1 -> Processor2 route logically separate from Processor3 ->
Processor4? If yes, put them in separate routes. Mark the "put on Google
PubSub" InOnly then it won't wait for a reply.
-Steve
> -Original Message-
> From: David Shubert
> Sent: Tuesday, April 20, 2021 11:20 AM
>
Steve
Yes, I broke these up into routes. I tried your idea by making processor4
throw an exception but Pubsub still redelivers the message. Did I put it
into the right place?
Thanks,
David
rest("myURL")
.post("lastPartOfURL")
.outType(String.class)
.route()
Hi,
It looks like something has changed between Camel 3.8.0 and 3.9.0 with
Groovy or CamelLoopIndex.
Up to and including Camel 3.8.0 my route succesfully runs the loop.
In Camel 3.9.0 the loop fails. A wild guess is that something changed in
accessing exchange.properties.CamelLoopIndex.
Hi
See the upgrade guide
https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_9.html#_exchange_properties
On Tue, Apr 20, 2021 at 11:44 PM Carl van Denzen wrote:
>
> Hi,
>
> It looks like something has changed between Camel 3.8.0 and 3.9.0 with
> Groovy or CamelLoopIndex.
>
> Up to
Hi
Try with
[exchange.property(CamelLoopIndex)]
Or
[exchange.allProperties.CamelLoopIndex]
On Tue, Apr 20, 2021 at 11:44 PM Carl van Denzen wrote:
>
> Hi,
>
> It looks like something has changed between Camel 3.8.0 and 3.9.0 with
> Groovy or CamelLoopIndex.
>
> Up to and including Camel
