Hi Cameleers,
we have been discussing introducing LTS/non-LTS releases on the
developers mailing list[1].
You also might have noticed a blog post on this topic[2].
I'd like to introduce the wider community to this, so please chime in
with your thoughts on this in this thread.
zoran
[1]
https:/
Hi,
I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use a
DeadLetterChannel and when the error has been handled, I expect the original
route to stop and not to continue.
When we use enrich we pass the exchange property CamelErrorHandlerHandled back
to ensure the calling r
Hi,
The files have been removed, so I post the import parts of it.
The strategy:
Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
oldExchange.in.body = newExchange.in.body
// Default Camel: Enricher.defaultAggregationStrategy()
// Default Camel: Enricher => CopyAggr
Would you mind raising a JIRA issue and attaching your test ?
I'll have a look at the problem.
Le lun. 9 mars 2020 à 15:48, Remco Schoen a écrit :
> Hi,
>
> I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use
> a DeadLetterChannel and when the error has been handled, I expe
Hi,
I raised an issue:
https://issues.apache.org/jira/browse/CAMEL-14684
Op 9 mrt. 2020, om 16:17 heeft Guillaume Nodet het volgende
geschreven:
Would you mind raising a JIRA issue and attaching your test ?
I'll have a look at the problem.
Le lun. 9 mars 2020 à 15:48, Remco Schoen
mailto:r.s
