Camel CLI (Camel JBang) provides an easy way to try Apache Camel without extensive configuration. It allows installing Camel dependencies with jbang, developing and running Camel integrations locally, and exporting projects to runtimes like Quarkus. Current features include dependency management, running Camel DSLs, hot reloading, and exporting to Spring Boot. Future plans include managing multiple integrations, improved health checks, and running on additional runtimes. Camel JBang aims to lower the barrier to experimenting with Camel.
14. Camel JBang
https://camel.apache.org/manual/camel-jbang.html
❏ Camel CLI
❏ Quickly run Camel integration
file(s)
❏ Automatic dependency
management
(no Maven or Gradle)
❏ All DSLs (java xml yaml
groovy kotlin)
❏ Hot reload on source change
❏ Export to Spring Boot or Quarkus
project (with Maven pom.xml)
15. Camel JBang
https://camel.apache.org/manual/camel-jbang.html
❏ Control running integrations
(list, start, stop, etc.)
❏ Control Spring Boot & Quarkus
Camel applications
❏ Runtime statistics
❏ Top routes and EIPs
❏ Show Camel route source
❏ View catalog of out of the box
artifacts
❏ View documentation
❏ Launch hawtio web console
New in Camel 3.19
18. Roadmap
Camel 3.19 (Oct 2022)
● Manage multiple Camel integrations
Camel 3.20 LTS (Dec 2022)
● Shell completer (Tadayoshi)
● Standard Maven (download JARs)
● Detailed health check information
● List JAR dependencies
● Export with gradle as build tool
● … many new commands (runtime information)
19. Roadmap
Camel 1H 2023
● Local configuration
● Decouple JBang commands from runtime Camel
● Switch easy Camel version (camel run foo.yaml –-version=3.18.3 )
● Run in SB/Quarkus (camel run foo.yaml --runtime=quarkus )
● Run in background
● Log command
20. Roadmap
Other Ideas
● Coloured output
● Java DSL without need for public class … { } wrapping
● OpenAPI generate DTO classes
● SOAP generate DTO classes
● Run OSGI blueprint XML routes (Grzegorz)