Skip to content
Weik.ioBlog
Try Weik.io

Camel 4.22 and 4.18 side by side

Weik.io 2026.2 ships two Camel lines, 4.18.5 and 4.22.1. You choose the one each integration runs on. Because integrations on both lines run next to each other on the same agents, you can move your integrations one at a time to a newer Camel line and test each move in devtest before it reaches production.

Choosing the line

An integration sets its Camel line in integration.yaml:

erp-invoice-export/integration.yaml
name: erp-invoice-export
version: 1.0.0
camelVersion: "4.18.5"

A folder without integration.yaml can set it in application.properties instead. Because the key is the one Camel JBang uses, a local run gets the same line:

application.properties
camel.jbang.camel-version=4.18.5

An integration that sets no line gets the installation's default. A platform admin sets the default with weikio settings set --default-camel-version. A range such as 4.22.x resolves to the newest patch of 4.22 that the installation lists. When the installation adds a newer patch of 4.22, Weik.io builds the next version of an integration with that range on the new patch:

invoice-archive/integration.yaml
name: invoice-archive
version: 1.4.2
camelVersion: "4.22.x"

weikio get camel-lines lists the lines the installation allows and marks the default. For each line you see the Java version it needs and the kamelet catalog pinned to it, and the digest of the launcher that builds the line.

What depends on the line

The build runs the tools of the integration's own line. On 4.22.1 it validates the routes with camel validate. A malformed route fails during the apply with Camel's own message. Next the build resolves the dependencies with camel dependency copy for that line and stores the jars of the version in Weik.io.

Each line has its own kamelet catalog, the 4.18 catalog for 4.18.5 and the 4.22 catalog for 4.22.1. A kamelet name resolves first to the integration's own folder, then to the five kamelets of the platform, then to the project's shared kamelets and last to the catalog of the integration's line.

On the agent, each line has a snapshot of the classes that every integration on that line loads. The Java processes of the line start faster from that snapshot and share part of it in memory.

Moving an integration to 4.22

Change camelVersion in integration.yaml. Then publish the folder as a new version and deploy it to devtest:

Terminal
$ weikio apply -f ./finance/erp-invoice-export --bump minor
Target: https://hub.example, project finance (from finance/project.yaml)
Uploading 2/9 files, building...
integration finance/erp-invoice-export updated (version 1.1.0, built in 17.3 s)
integration.yaml updated to 1.1.0

Nothing new is running yet. To run it:
  weikio deploy -f ./finance/erp-invoice-export --env devtest

weikio get versions shows which line each environment runs. It lists every version with its Camel line in the CAMEL column and the environments it's deployed in.

When the new version has run in devtest, weikio promote moves it to production without a new build. If something on the new line misbehaves there, weikio rollback points production back at the previous version. That version runs on its own line with its own jars. Months after a version was built, weikio describe version still prints its exact jar set.

What comes next

Weik.io 2026.2.3 focuses on Camel versions and on running more lines side by side, such as a third line next to 4.18.5 and 4.22.1. Read Where Weik.io is going for what's coming.

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo