Update Talend 7.1.1 => 7.2.1: Update Java 11

[Anonymous]

Hi

i'm currently working on updating Talend and Java.

So far i could succesfully update vom Talend OS ESB 7.1 to Talend OS DI 7.2.1 (we dont need the ESB-Part anymore). With existing Java 8 everything runs fine. Now i'm trying to Update from Java 1.8 to Java 11.

On my local computer Java 11 is installed:

Also JAVA-HOME and JRE_HOME point to JDK 11:

Its also included in PATH: (First and only entry pointing to Java there):

If i start old Talend 7.1 it is not working anymore.

If i start Talend 7.2. it starts normal and project is imported.

So it seems fine to me.

But my problem is that i can't set the Java compiler compliance to 1.11 in Studio. In Project settings my only option is 1.8:

In preferences i have following Settings:

In Preferences->Java->Compiler i can change "Compiler compliance level":

If i choose 1.8 there it even warns me about:

But the setting there is not saved. It doesnt seem to have any effect and when i restart Talend its again reset to 1.8. I can not set and keep Java 11.

If i build after set to 11 there it still runs with Java 8.

Can anyone help me here? I don't know what else i can do anymore.

Thank you und kind regards,

Sven

[Anonymous]

I found following entries in the Talend Studio workspace .log:

!ENTRY org.talend.platform.logging 2 0 2020-03-13 10:50:53.415
!MESSAGE 2020-03-13 10:50:53,414 WARN org.talend.commons.exception.CommonExceptionHandler - Missing module group definition: esb-java-11-group

!ENTRY org.talend.platform.logging 2 0 2020-03-13 10:50:53.428
!MESSAGE 2020-03-13 10:50:53,427 WARN org.talend.commons.exception.CommonExceptionHandler - Missing module group definition: esb-java-11-group

Is this known to anyone?

I still have the same troubles as described above and can't get it to work.

[Anonymous]

I installed Talend OS DI 7.3.1 now. In preferences Java 11 is now selected.

But still in project properties i see only Java 1.8.

Has no one had similar problems? Is it working for you with Java 11?

[t_leitner]

Hello @Sven1991 !

I basically have the same problem as you. I installed the current version of Talend Studio for Data Integration, 7.3.1 and the Java 11 OpenJDK from Zulu.

But I cannot permanently select Java 11 in Windows->Preferences->Java->Compiler. When I select 11 and the re-open a job or restart Talend Studio, Java 1.8 is again selected.

Also in File->"Edit project properties"->Build->Java Version in the Compiler Compliance Level I only can choose Java 1.8.

But I think I should choose Java 11 here, but it is not listed.

In the "Installed JREs" section in the Preferences, everything is correctly selected for the Zulu-11 JDK.

The problem also is, that I wanted to create a job using a tESBConsumer component, but Studio seems to be generating Java 8 code, because a class javax.xml.soap.SOAPFault is generated here, but this class was removed in Java 11.

So I cannot compile or build the job, because I only have Java 11 JDK installed.

Did you find any solution to use Java 11 with Talend Studio 7.3.1?

[Anonymous]

Hello

No worries, what you can see isnot java version 1.8 , but compliance level=8 .

IT means the generated bytecodes will be on format to run with java 8 and all newer release.

Nothing to worry about, and I recommand you to let you compliance level= 8: you builds could be run with a java 8

What saysstudio to you is "you have java 11, and if you build a job, I'll build bytecodes that can run under uner java 8 minimum release"

More information about java compliance :

https://stackoverflow.com/questions/22584427/what-is-compiler-compliance-level-in-eclipse

[t_leitner]

@David Lucas​ 

Thank you very much for your response!

Yes, you are right, I think the 1.8 compliance level is not the problem in my case.

In my case, the problem was, that when using tESBConsumer with Talend Cloud Data Integeration entry level license, there was an error, that javax.xml.soap.SOAPFault is not found.

I THOUGHT that this was a java version problem, because this package was removed in Java 11. But now together with Talend Support we found out, that the problem actually is the component tESBConsumer in Talend Studio v7.3.1 with Data Integration license.

Our contact at Talend tried it with a Big Data license and everything worked, but with Data Integration license, there was this compilation error. It turned out that in Data Integration the module for jakarta.xml.soap-api is missing in the tESBConsumer component, while with Big Data license it is there.

So the generated Java Code of tESBConsumer seems always to contain the javax.xml.soap.SOAPFault class but the component SHOULD have a module with an external jar for the implementation.

But this is missing in our case with our license

So basically this makes tESBConsumer unusable for us right now. We will use tSOAP for now.

Our Talend contact has opened an internal Ticket with Talend Tech Support and hopefully he will find out if this is a bug or a feature. But I think if Talend doesn't want Entry level license customers to use tESBConsumer they should have removed the component alltogether and not make it buggy 🙂

[Anonymous]

Hello

Do you run TOS DI 7.2.1 or TOS ESB 7.2.1 ?

Sven were using TOS DI 7.2.1 , if you're in same case, please use TOS ESB 7.2.1

You mays have a look also here:

https://stackoverflow.com/questions/54573998/java-11-package-javax-xml-soap-does-not-exist/54574003

Looks like the feature has been removed from java, not from talend, and Talend supports also jdk 8, where the lib is not depreated , that's why Talend did not remove the feature

[t_leitner]

@David Lucas​ 

Thank you for your response!

I am not using "Talend Open Studio", but "Talend Studio". My company has a Talend Cloud Data Integration license, which seems to be the entry-level license.

So I don't think I just can switch to "TOS ESB x.x.x", because I can only download "Talend Studio" from my Talend Cloud Interface.

Also I am using the latest version 7.3.1 of Talend Studio.

Yes, I am aware that javax.xml.soap was removed from Java 11. That's why I first thought that this would be a Java problem. But Talend is recommending Java 11

https://help.talend.com/reader/NkKh400tF3Z4O8jjJ23uUQ/3CeQrjaMkxbHNySnAgRXcw

I installed Zulu OpenJDK 11.

I already clarified this issue with our Talend Consultant Aniket Band. He was able to reproduce it and the support ticket is currently in "Investigation".

Aniket found out that with Java 11 there should be external modules be added in the component tESBConsumer in Talend Studio. He compared the modules in Data Integration license vs. Big Data license. With Big Data license he had the module jakarta.xml.soap-api-1.4.1jar in the module, whichs seems to be the jar file that includes the package javax.xml.soap. But with Data Integration license this module was missing. So this SEEMS to be the problem.

I think it needs to be clarified now, why this module is missing in Data Integration.

Maybe everything would work with Java 8. But since Talend recommended to install Java 11, we installed Java 11 on all our remote engines and our Dev Machines.

So currently I am basically waiting for an official answer from support about this issue 🙂

[reinierD]

Was this issue ever resolved. We also run into this, and would like to know if there is an easy way to upgrade projects that were started in Java8 to Java11, without having to manually include jar files using tLibraryLoad (which is the workaround we found)

[t_leitner]

Hello @Reinier Battenberg​ 

Yes, the issue was resolved for us - kind of.

We had two open Support Cases at Talend Support, one for the Java 11 problem with tESBConsumer and one for the Java 11 problem with tRESTClient.

So basically we could not build or execute Talend Jobs in Talend Studio 7.3.1 with Data Integration license using Java 11. Because with Java 11 the components tESBConsumer and tRESTClient both were buggy, some extra needed files were missing (this was described in more detail in previous posts).

But Talend managed to fix theses issues with the components. Talend Support sent us patches for Talend Studio 7.3.1 that contained the fixes. We tested the patches with Java 11 and it really worked for us.

But because we wanted to keep the base-Version 7.3.1 of Studio for development of our Jobs, we still use Java 1.8 for development now.

So I know that theses Java 11 issues in tESBConsumer and tRESTClient have been patched by Talend, but we are now waiting for the next major release 7.4 of Studio. I hope the patches will be included in the next version, then we will try to migrate vom Java 1.8 to Java 11 once again.

I hope this information is helpful to you.

Kind regards

Thomas Leitner