- Works fine on 6.3.1:
The java/bean usage is as follows. Create a java class/bean within Talend Studio's Integration perspective > Code/beans. Then switch to java perspective (Package explorer) , right click on the Project/code and export as Jar. In this case, it will list some pom*.xml files within Code folder for export. Select all and then create the jar ignoring some exception/error pop-up. Then switch to Mapping perspective , new > Database , edit class path and add the jar. Next in a Map, one can access the routine by using Java function passing the packagename and class name (for example beans.MyClass) followed by routine(and it's arguments). .This works fine in 6.3.1.
- How is this done on 6.4.1 and higher versions ?!
We have noticed that in Studio 6.4.1, it doesn't show any option to import the jar file onto TDM class path(attached screenshot). Ideally (could be a feature request) it would have been great if we could access the bean class directly without having to import any jar files.
Solved! Go to Solution.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Learn how to use an API-First Approach to Modernize your Applications