Ask an AI coding assistant to write an Apache Camel route and you will likely get working code on the first try. Ask it to configure a Kafka consumer, wire up an error handler, or transform a message with the Simple language, and the result is usually correct — often surprisingly so. This is not because AI models were specifically trained on Camel. It is because Camel’s 19-year track record has produced exactly the kind of public, high-quality, consistent data that large language models learn best from.
, by Ricardo M., Tomo Igarashi, Paloma Vinaches Melguizo, Dominik Jelínek, Matej Melko
What’s New? Kaoto 2.11 delivers major improvements across three key areas: automated testing through Citrus framework support, enhanced DataMapper capabilities for handling complex schemas, and flexible runtime management options. Built on Apache Camel 4.20.0, this release strengthens Kaoto’s position as a powerful visual integration design tool. Citrus Testing Capabilities The Citrus framework is now fully integrated into Kaoto 2.11, enabling you to create automated tests within the same visual environment where you design your integrations.
Every Apache Camel release ships new features and bug fixes — and those get the headlines. But behind every release there is a quieter effort that rarely gets mentioned: keeping 500+ third-party dependencies current. We compared the parent/pom.xml across every Camel 4.x minor release — from 4.0.0 to 4.20.0 — and counted every dependency version that changed. Here is what we found. 2,449 dependency updates across 20 releases Every minor release updates a significant portion of the dependency tree.