Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Discover how organizations are unlocking new revenue streams: Watch here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

How long Talend will support the JET based components?

I am facing the problem, most of the users of my components are not running Talend 7+. In fact a lot of them are stick with Talend 5.x.

The new approach to develop components is on my opinion not really fully functional. There are lacking a couple of features like conditionally disable input widgets or tables in tables and I am missing labels and the release cycles of the new API are quite short and fast.

I have to decide when I have to change to the new development approach.

Where is a timeline about the change and compatibility?

Labels (1)
  • v7.x

5 Replies
Anonymous
Not applicable
Author

Hi @lli,

 

The JavaJet approach will not be dropped shortly from the Studio however it is a deprecated way to build custom components for the coming Studio versions. If your customers stay on Talend 5.x you will have to stay aligned on that however if you target new components and users you should use the Kit framework.

 

On the release cycle: you have to keep in mind the framework is a 360° solution so it covers from the component development (javajet scope) to the testing (JUnit and so on) until the web ui rendering since this framework will enable you to work in all Talend platforms including cloud ones. This implies that releases can be more frequent to help people blocked by either bugs or missing features. It does not mean that you have to follow all single releases. In particular, if you want to work only in the studio, you have to use the version which is supported by the Studio version you target.

 

On the lack of features you are more than welcomed to open tickets on our jira: jira.talendforge.org/projects/TCOMP/. However we don't aim at replacing all Studio features since we cover at the same time the web and the Studio so some UI habits can have to be adapted to cover both environments without making your component laggy or unresponsive.

 

Hope it helps,

Romain

Anonymous
Not applicable
Author

Dear Roman,

thanks very much for your kind answer. Yes I was a bit worried because you know I do not have a company on my own, I have to reengineer all of my components for my self, so I have a lot of work to do.

I really hope we can improve the studio UI a bit and of course such improvements must be adaptable also for the web UI.

I will track the component sdk project and will start building sdk versions of my existing components.

Best regards

Jan

Anonymous
Not applicable
Author

Thanks for the answer. I am not allowed to file tickets or view tickets in the TCOMP project.

Could you please open it for me?

Best regards

Jan Lolling

Anonymous
Not applicable
Author

Hi Jan,

 

Can you give it another try please? Seems we got some Jira update recently and it should be accessible now.

Anonymous
Not applicable
Author

Thanks a lot, now I can see the tickets of the TCOMP project. I will check if there is already a ticket for my issue and otherwise I will file such ticket.