A few weeks ago I presented Camel JBang at the Quarkus Insights show and one of the demos I did was to quickly run Camel 1.0 route copied with the latest Camel.
This is a 4-minute recording of that demo.
If you want to see more, then I recommend to watch the Quarkus Insight session.
Related posts
Camel presented at Quarkus Insights
, by Peter Palaga, Zineb BENDHIBA, Claus IbsenApache Camel was recently showcased at the Quarkus Insights show (#110). The session runs 1 hour and 10 minutes, where Peter first give an overview of Apache Camel, then Claus presents the latest update on Camel JBang, and with live demos. And the last 40 minutes is focused on Camel Quarkus where Zineb shows a live coded demo. The recording can be watched from YouTube.
How to test an Integration for Camel K
, by Pasquale CongiustiTesting is probably one of those operations we use to repeat most of the time while building any application. Applications in Camel world are no difference. With the advent of Camel JBang, we have a unified place that can be used to perform our testing/fine tuning locally before moving to a higher environment. During the last years of development, we have noticed that testing or fine tuning an integration directly connected to a Cloud Native environment can result a bit cumbersome.
Camel Designer's new mapping system
, by Bruno Meseguer\ A new input mapping system has been added to Camel Designer. But what that even means ?!? Well, better to be seen, but if explained, it’s an effort to provide a more intuitive configuration system for Camel route steps. On one hand, it simplifies the view of a route by compacting route steps, and on the other hand, it provides an easy drag-and-drop mapping ability to map process variables to activity inputs.
Camel + JBang: bringing the world of Java scripting to Camel
, by Otavio Rodolfo PiskeBringing the world of Java scripting to Camel
Apache Camel and CVE-2021-44228 (log4j)
, by Claus IbsenApache Camel is NOT using log4j for production Apache Camel does not directly depend on Log4j 2, so we are not affected by CVE-2021-44228. If you explicitly added the Log4j 2 dependency to your own applications, make sure to upgrade. Apache Camel is using log4j for testing itself Apache Camel does use log4j during testing itself, and therefore you can find that we have been using log4j v2.13.3 release in our latest LTS releases Camel 3.