Core framework updates of Talend ESB for 8.0.1-R2023-08 - 8.0

Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend ESB
Talend Runtime
Talend Studio
Design and Development
Installation and Upgrade
Last publication date

Core framework updates of Talend ESB for 8.0.1-R2023-08

Talend 8.0.1-R2023-08 release upgraded the core framework of Talend ESB:

  • Apache Camel 3.11.1 to 3.20.6
  • Apache CXF 3.4.10 to 3.5.5
  • Apache Karaf 4.2.11 to 4.4.3
  • Apache ActiveMQ 5.16.3 to 5.17.4
  • Spring Boot 2.6.8 to 2.7.12
This article introduces the dedicated changes of this upgrade.

If you are using Talend Runtime for deployment, after installing the R2023-08 Studio patch, you need to use exclusively the R2023-08 Talend Runtime build because the Camel version for Studio and Runtime must be aligned. You will need to rebuild, republish, and redeploy all your Data Services and Routes.

For more information on the upgrade process, see Upgrading Talend Runtime for on-premises deployment and Upgrading Talend Runtime for Cloud.

Apache Camel

Apache Camel is upgraded from 3.11.1 to 3.20.6.

New Camel components are available in the new version and some old components are removed. For example:

New components Added from version
camel-dynamic-router 3.15
camel-elasticsearch 3.19
camel-hashicorp-vault 3.18
camel-influxdb2 3.20
camel-json-patch 3.12
camel-knative 3.15
camel-mapstruct 3.19
camel-plc4x 3.20
camel-rocketmq 3.20
camel-whatsapp 3.19
Removed components Removed from version
camel-ahc 3.19
camel-ahc-ws 3.19
camel-atomix 3.17
camel-beanio 3.17
camel-beanstalk 3.17
camel-elsql 3.17
camel-etcd 3.17
camel-ganglia 3.17
camel-hystrix 3.17
camel-jing 3.17
camel-kamelet-reify 3.17
camel-leveldb-legacy 3.17
camel-msv 3.17
camel-nagios 3.17
camel-nsq 3.17
camel-ribbon 3.17
camel-sip 3.17
camel-soroush 3.17
camel-spring-javaconfig 3.15
camel-tagsoup 3.17
camel-yammer 3.17
New features are available for Talend ESB use cases:
  • Modern Authentication support for cMail Component
  • Camel cWMQ enhancement requests

Apache CXF

Apache CXF is upgraded from 3.4.10 to 3.5.5 with bug fixes (security included) and improvements added.

Apache Karaf

Apache Karaf is upgraded from 4.2.11 to 4.4.3, which is the most up-to-date release for this OSGi container.

While preparing support for Java 17, Java 11 remain the recommended Java version to use.

Apache ActiveMQ

Apache ActiveMQ is upgraded from 5.16.3 to 5.17.4 with bug fixes and improvements added.

Spring Boot

Spring Boot is upgraded from 2.6.8 to 2.7.12, aligned with Camel requirements.

Impacts of the core framework updates of Talend ESB for 8.0.1-R2023-08

The impacts of the core framework updates of Talend ESB for 8.0.1-R2023-08 are only for users deploying Talend Runtime features.

Microservices (Spring Boot) users are not impacted. They will benefit from new core libraries versions when re-building Routes and/or Data Services. There is no extra work for this kind of usage.

Starting from Talend Studio 8.0.1-R2023-08, all Data Services and Routes built/published with Talend Studio/CI prior to 8.0.1-R2023-08 become incompatible with the new Talend Runtime 8.0.1-R2023-08.

Feature Known breaking changes
Karaf version upgrade to 4.4.3 Core upgraded.
Camel version upgrade to 3.20.6 LTS
  • CAMEL-9627, CAMEL-14778: Routes with cSOAP/cREST are affected, including package names (for example, CxfHeaderFilterStrategy, CxfPayload) and generated features.xml.
  • CAMEL-17291: Routes with cAWSSES are affected.
  • CAMEL-17638: Routes with cRecipientList/cSplitter/cXMLParser/cXMLWriter are affected.
  • CAMEL-17296: Routes with cMulticast are affected.
  • CAMEL-17499: Routes with cXMLParser/cXMLWriter/cJavaDSLProcessor are affected.
  • CAMEL-17668 Routes with cWireTap are affected.

New Camel components added in cMessagingEndpoint from 3.20.6 are not supported by Talend Runtime prior to 8.0.1-R2023-08.

Removed Camel components in cMessagingEndpoint from 3.20.6 are not able to be built anymore from Talend Studio 8.0.1-R2023-08 and later.

CXF version upgrade to 3.5.5 After CXF upgrade in Talend Studio, Jackson version conflicts between Talend Studio (2.14.1 in 8.0.1-R2023-08) and Talend Runtime (2.13.2 before 8.0.1-R2023-08).

Known issues about the upgrade to 8.0.1-R2023-08

APPINT-35562 Fail to run route as microservice docker image with java.lang.UnsupportedClassVersionError

Camel 3.20.6 libraries are built via JDK 11, which require JDK 11 configured in Dockerfile for running the Docker image.

A ticket has been created to have a permanent fix.

As a workaround, you can configure the talend.docker.jdk property before building/publishing the Docker image in the Project settings of Talend Studio:

Or via the CI builder:

mvn clean deploy .... -Dtalend.docker.jdk=openjdk:11 ...

Frequently asked questions about the upgrade to 8.0.1-R2023-08

Where can I get the Talend Runtime 8.0.1-R2023-08 archive or installer?

If you are using Talend Cloud, you can download Talend Runtime from the Talend Cloud download page.

If you are using on-premises Talend products, the 8.0.1-R2023-08-RT deliverables are available for download on The license credentials issued with your original Talend 8.0.1 product subscription will be required for the download. Please contact Talend Support if you miss these credentials.The download link is determined according to the product license you have subscribed to. Please replace the license placeholder in the following URLs with the appropriate short name:
The license short names corresponding to Talend product names are:
  • Talend ESB 8.0.1: "esbee"
  • Talend Data Fabric 8.0.1: "tdf"
  • Talend MDM Platform 8.0.1: "tpmdm"
  • Talend Data Services Platform 8.0.1: "tpds"
  • Talend Real-Time Big Data Platform 8.0.1: "tpdsdrt"

For example, the download link for the Linux installer corresponding to the Talend ESB 8.0.1 license is

Do I need to upgrade my Remote Engine?

Upgrading your Remote Engine is not a requirement, but if you are not using the latest version of the Remote Engine, it is a good opportunity to upgrade it.

Are my already published artifacts compatible with the new Talend Runtime 8.0.1-R2023-08?

No. Breaking changes brought by the third-party libraries cause the old artifacts to become incompatible with the new Talend Runtime. A new publish is required for all Routes and Data Services.

Deploying an old artifact in the new Talend Runtime will fail and add a message in Talend Runtime logs telling that the artifact is not compatible.

What if I deploy a newly published artifact from 8.0.1-R2023-08 in an old Talend Runtime?

Deployment will fail silently. Old Talend Runtime does not include any mechanism that could detect a version incompatibility.

How can I recognize an artifact which is newly built with version 8.0.1-R2023-08 from an older artifact?

You can define rules about artifacts versioning or artifacts naming.

Can I use Talend Runtime migration tooling provided with recent patches to automate migration to 8.0.1-R2023-08?

No. The provided tooling helps if artifacts deployed in the source Runtime are compatible with the target Runtime. Here it is not the case. Even Runtime configuration must be manually migrated.