Apache Camel 3.x Upgrade Guide

This document is for helping you upgrade your Apache Camel application from Camel 3.x to 3.y. For example if you are upgrading Camel 3.0 to 3.2, then you should follow the guides from both 3.0 to 3.1 and 3.1 to 3.2.

Upgrading Camel 3.19 to 3.20


The org.apache.camel.support.jsse.SSLContextParameters is now using ResourceLoader from CamelContext to load keystore and other resources in a standard way. Therefore, the SSLContextParameters now must have been pre-configured with a CamelContext otherwise an exception is thrown.


The camel-bom BOM no longer includes dependencies with <type>test-jar</type> as these are for internal testing of the Apache Camel project.

The following Maven Plugins has been fixed to use correct GAV:

  • camel-debezium-maven-plugin

  • camel-salesforce-maven-plugin

  • camel-servicenow-maven-plugin

from <groupdId>org.apache.camel</groupdId> to <groupdId>org.apache.camel.maven</groupdId>.

Dependencies not intended for end users has been removed, such as all -parent JARs.


There is a new option unpackArray that unpacks a single-element Json array, matched by a Jsonpath, into an object. This option is disabled by default (this behaviour was enabled by default in previous Camel versions). There is a new expression jsonpathUnpack(String text, Class<?> resultType) that makes use of this new option.


The headers used by the Camel Google Pubsub component has been renamed. The prefix CamelGooglePubsub. has been updated to CamelGooglePubsub without any dot. This is related to CAMEL-18773 issue.