Unable to load custom component from the "creating your first component" tutorial

[mikael_lb]

Hi,

I'm new to talend so I have followed the tutorial to create a first component. After solving maven issues I can build it but can't see it in the palette. No message in log.

After lots of search on this forum i've decided to restart the process from scratch by installing a fresh TOS (v8.0.1), get a zulu JDK11 as mentionned in requirements, delete .m2, etc...

I use the starter toolkit https://starter-toolkit.talend.io and follow the tutorial for the 4th time.

Then mvn clean install => Build success

and mvn talend-component:deploy-in-studio `-Dtalend.component.studioHome="C:\TOS_DI-8.0.1\studio" `-Dtalend.component.enforceDeployment=true -f pom.xml => Build success

Then check component.java.registry => ok

and components-registration.properties =>ok

Then start TOS, no custom component in the palette and check log and I've this time this error :

An idea ?

[undx]

Hello @Not defined Not defined​ ,

This is strange, those errors should not happen w/ a jdk11, we usually have this kind of issues w/ jdk15+.

Could you try to add the following jvm flags at the end of your `Talend-Studio-<platform>.ini` :

```

--add-modules=ALL-SYSTEM

--add-opens java.base/java.io=ALL-UNNAMED

--add-opens java.base/java.lang.invoke=ALL-UNNAMED

--add-opens java.base/java.lang.reflect=ALL-UNNAMED

--add-opens java.base/java.lang=ALL-UNNAMED

--add-opens java.base/java.net=ALL-UNNAMED

--add-opens java.base/java.nio=ALL-UNNAMED

--add-opens java.base/java.util=ALL-UNNAMED

--add-opens java.base/java.util.concurrent=ALL-UNNAMED

--add-opens java.base/sun.nio.ch=ALL-UNNAMED

--add-opens java.base/sun.nio.cs=ALL-UNNAMED

--add-opens java.base/sun.security.action=ALL-UNNAMED

--add-opens java.base/sun.security.x509=ALL-UNNAMED

--add-opens java.base/sun.util.calendar=ALL-UNNAMED

```

Respect the format of the ini file (not the same as code below).

Then restart your studio.

Best regards

[mikael_lb]

Hello @Emmanuel GALLOIS​ ,

Thanks for your answer.

.

So I write the lines at the end of the ini file and restart TOS. The palette takes time to appear but no custom component. No new things in the log too.

.

After that I uninstall and install TOS another time and strange thing, it works. I can see th custom component in the palette (even if there is a huge {"code":"UNEXPECTED"} error in the log file).

.

So I will continue the tutorial.

.

Best regards

[mikael_lb]

Hi everyone and @Emmanuel GALLOIS​ 

Last step in the tutorial is to launch the job with the custom component.

I don't know if it is helpful to solve the issue but the capture below is the console output.

And also link as file : the complete log file from start of TOS to end of job's run.

Thanks for your advices.

[JReynard]

I have the same problem. Did you fix it ?

[mikael_lb]

Hi @Jérémy Reynard​ 

No I don't fix it but if you have you are welcome to share the fix here

Best regards

[undx]

Hello,

That's an issue that we meet only in TOS product because Dynamic types aren't present in TOS.

This needs to be fixed...

Regards