Hi, there. I'm experiencing something weird here and I'm desperate for an
answer.
I realize this is a long message, but it's only because I'm verbose.
It's a really straight forward setup, so I'm hoping it's just an obvious
configuration issue...
I have a simple Server and Client setup for s
No Camel 2.22.1 is not supported to run on JDK 11. We are working on making
stuff work on JDK 11. No defined date for the moment.
Yes, it should work fine on 4.2.1.
Il mer, 12 set, 2018 alle 19:15, Swaminathan,
Arun ha scritto: Hi all,
We have a project involving migration to java11.
Cou
Hi all,
We have a project involving migration to java11.
Couple of questions:
- Does camel 2.22.1 support running under Java11? If not, when is the support
planned?
- is camel 2.22.1 compatible with Apache Karaf 4.2.1 which was recently
released.
Thx,
arun
Hi,
Is there a way for the .aggregate to keep firing until predicate is satisfied?
Like this:
from("direct:database-save")
.log("Fetch 500 records until no more ")
.aggregate(constant(true), batchAggregationStrategy())
.completionPredicate().simple("${body.get('offset')} != -1")
.completionTim
A new security advisory has been released for Apache Camel, that is fixed in
the recent 2.20.4, 2.21.2 and 2.22.1 releases:
CVE-2018-8041: Apache Camel's Mail is vulnerable to path traversal
Severity: MEDIUM
Vendor: The Apache Software Foundation
Versions Affected: Camel 2.20.0 to 2.20.3, Camel
A new security advisory has been released for Apache Camel, that is fixed in
the recent 2.20.4, 2.21.2 and 2.22.1 releases:
CVE-2018-8041: Apache Camel's Mail is vulnerable to path traversal
Severity: MEDIUM
Vendor: The Apache Software Foundation
Versions Affected: Camel 2.20.0 to 2.20.3, Camel 2