Apache Camel 3.5 has just been released. This is a non-LTS release which means we will not provide patch releases, but use the release as-is. The next planned LTS release is 3.7 scheduled towards end of the year. So what’s in this release? This release introduces new set of features and noticeable improvements that will we cover in this blog post. Java 14 This is the first release that supports Java 14.
We recently released camel-kafka-connector 0.4.0. This is the first release of the latest project in the Camel’s ecosystem, based on an LTS camel release. The main features of this release are: Introduction of aggregation support Introduction of marshalling and unmarshalling support on both sink and source connectors Upgrade to the latest Apache Camel release 3.4.2 Addition of new examples in the camel-kafka-connector-examples repository Integration tests added for HDFS (sink), Cassandra/CQL (source), Slack (Source), JDBC (sink) and MongoDB (sink/source).
Camel and Camel Quarkus are typically used to create integration applications that run as long living processes, a.k.a. daemons or services. In this blog post, we are going to explain a slightly different use case: using Camel Quarkus in programs that exit by themselves after performing some desired tasks. Where can this be useful? The enterprise is full of scheduled batch processing. Say, some system exports some sort of reports daily at 4 a.