Apache Camel Quarkus 1.4.0 has been released! We continue to integrate with the latest Camel and Quarkus releases, whilst adding new features and fixing bugs. For a full overview of the changes see the 1.4.0 milestone details. Here are some of the highlights. Major component upgrades Quarkus 1.10.0 New extensions As ever, we added some new extensions and enhanced existing ones with native support. 1 new JVM only extension was added:
Even implementing a simple stateless micro-service, one could face situations where testing becomes hard. A lot of tools and techniques could help, but having something at hand quickly is very handy. In this post, I’m introducing a Quarkus feature that plays nice with Camel in order to mock beans for test purpose. Camel and Quarkus together for mocking beans It’s long known that Camel offers great support for Java beans.
The highlights of Camel Quarkus 1.2.0 and 1.3.0
Apache Camel Quarkus 1.1.0 has been released! We continue to integrate with the latest Camel and Quarkus releases, whilst adding new features and fixing bugs. For a full overview of the changes see the 1.1.0 milestone details. Here are some of the highlights. Major component upgrades Camel 3.5.0 Quarkus 1.8.0 New extensions We added a whopping 174 new extensions in this release! This is because Camel Quarkus will shortly become the only and default runtime in our sibling project Camel K.
Enjoy the first maintenance release in the 1.0.x branch of Camel Quarkus! What’s inside Highlights: Camel 3.4.3 Quarkus 1.7.1 Details: All changes since 1.0.0 What’s next? Camel Quarkus 1.1.0 will be released shortly after Camel 3.5.0. We will possibly release some candidate releases (CRs) depending on the availability of Camel 3.5.0 CRs. To get an idea which new extensions are coming, look for the extensions having since = 1.
Walk through the highlights of the first stable release: Developer joy, Camel component coverage, Bootstrap, CDI, native mode and more!
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.
We are pleased to announce the release 1.0.0-CR3 of Camel Quarkus. Camel Quarkus brings the outstanding integration capabilities of Apache Camel to Quarkus - the toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. Here are some highlights of Camel Quarkus 1.0.0-CR3. New extensions The following new extensions were added: AWS 2 Athena Component DSL JOLT JTA OpenApi Java Tika Vert.x The following extensions added native mode support:
We are pleased to announce the release 1.0.0-CR2 of Camel Quarkus. Camel Quarkus brings the outstanding integration capabilities of Apache Camel to Quarkus - the toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. So what is new in Camel Quarkus 1.0.0-CR2? New bits While we do not have any new extensions this time, the following extensions were promoted from JVM-only to JVM+native: REST OpenApi Avro data format MongoDB GridFS Debezium PostgreSQL Debezium MySQL All supported bits can be seen in the List of Camel Quarkus extensions.