Talend Job error( issue with tRest client) after updating from Java 11 to Java 17

[sushantkapoor19]

Hello All,

We recently updated TAC ( Talend Adminstration centre) from Jdk 11 to jdk 17. one of our production jobs which uses tRest client  with PUT/POST method to SAP is failing due to below error:

Exception in thread "main" java.lang.IllegalAccessError: superclass access check failed: class nu.xom.JDK15XML1_0Parser (in unnamed module @0x770c2e6b) cannot access class com.sun.org.apache.xerces.internal.parsers.SAXParser (in module java.xml) because module java.xml does not export com.sun.org.apache.xerces.internal.parsers to unnamed module @0x770c2e6b
at java.base/java.lang.ClassLoader.defineClass1(Native Method)

When i run this job manually in Talend studio v 8.0 ( R2025-02) it gives me the below error,

Execution failed :org.talend.commons.exception.PersistenceException: The Job "SAP_Supplier_Informations_Info_Part2_SK_20250313" has wrong configuration. Fix it and try again.
Error Line: 20761
Detail Message: The type javax.ws.rs.client.ClientBuilder cannot be resolved. It is indirectly referenced from required type org.glassfish.jersey.client.JerseyClientBuilder
[The Job "SAP_Supplier_Informations_Info_Part2_SK_20250313" has wrong configuration. Fix it and try again.
Error Line: 20761
Detail Message: The type javax.ws.rs.client.ClientBuilder cannot be resolved. It is indirectly referenced from required type org.glassfish.jersey.client.JerseyClientBuilder]

has anyone faced this issue before? How to fix this as it is a crictical job impacting our production environment.

[gouravdubey5]

Hello,

Issues with tRESTClient after upgrading Talend Studio are typically related to library and dependency changes between versions.

After an upgrade, existing jobs may still reference older REST/HTTP libraries, which can cause compilation or runtime errors. This commonly affects components such as tRESTClient that rely on Apache CXF or related HTTP client libraries.

Recommended actions:

Open the Modules view and install any missing dependencies required by tRESTClient.

Remove and re-add the tRESTClient component to ensure it uses the updated component definition.

Review and reconfigure component properties, as some settings may have changed or been deprecated between versions.

Clean and rebuild the job to force Java code regeneration.

Verify the release notes of the target Studio version for any known REST-related changes.

Note:
This behavior is expected after major version upgrades and does not usually indicate an issue with the REST endpoint itself, but rather with design-time dependencies.

Thanks,

Gourav