Question I
Will the method to upgrade to Java 17 be the same as: upgrading-java-for-talend-remote-engine when a Remote Engine is already installed (from lower version like 8 or 11)?
The method is not the same for Java 17. Starting from Remote Engine version 2.13, it requires Java 17.
The document is only valid for Remote Engine versions 2.12 or lower.
From Remote Engine versions 2.13 and up, it will be required to re-install the Remote Engine.
Question II
Will the method of setting up Java 17 in Talend Studio remain the same as: setting-compiler-compliance-level ?
The answer is YES .
Question III
How will Camel components in route be used?
It is a matter of dependency management. Once Studio will be upgraded to 8.0.1-R2025-02 (Java 17/Camel 4), any newly created routes or existing routes will depend on Camel 4 so
appropriate libraries will be used at build/run time (either installed in Studio with update, or downloaded).
It is the same for all route components. It will be pretty transparent for the final user.
Question IV
Where is Camel 4 bundled?
Camel 4 libraries are either installed in Studio, or downloaded. OSGi features for Camel 4 are also pre-installed in Talend Runtime.
Either users deploy routes as Microservices and Camel 4 dependencies are packaged in fat Jar at build time or users deploy in Talend Runtime and the container (which new version will be delivered in Feb. 2025) includes all pre-installed Camel 4 features.
Additionally, the Remote Engine has nothing to do with Camel 4.
Related Content
If you are looking for more information about Java 17 Migration Guide, please refer to this KB article
Qlik-Talend-Products-Java-17-Migration-Guide
Environment
Talend Cloud
