I have a job that incldes a tRest component which calls a web-service.
All is configured well, but when running the job I get the following warning :
jul. 30, 2024 10:07:31 A.M. org.glassfish.jersey.client.innate.inject.NonInjectionManager <init> WARNING: Falling back to injection-less client.
The call to the webservice succeeds, data is retreivable, but where comes this warning from ? I reinstalled Talend Studio, upgaded to R2024-07, installed the additional libraries when I open the job for the first time.
But when a component is not specifically for ESB, then why is it selectable when creating a flow ? I think is should be not that difficult that components that are not appropriate for ESB but mainly for DI, get filterd out or marked in a way that developers can see if they made the right choise.
Besides that, jlolling said it was a missing jar. Why is that jar not in the Talend/Studio libray then, problem solved and you don't have to worry about picking a component that is for ESB and not for DI.
To build Jobs that need to be deployed into the Talend Runtime, it is recommended to use the tRESTClient component which is best suited for the Talend Runtime.
For your second issue about this missing jar issue in tRest component, I will check it with our R&D team and come back to you as soon as we can.
Support replie: Add the two jars : jersey-injectless-client-3.1.8.jar and jakarta.activation-api-1.2.2.jar, it will go directly to the injectless client instead of trying first the inject client.
Please provide instructions how to properly install this module in Talend Studio so the error will be resolved.
Please do not give answers like "don't use the tRest component, but instead use the tRestClient component".
Please solve this issue for people having this problem. I am included. I am having this issue. And when I make many tRest calls the job runs out of memory, probably because the log data being saved is growing so large.
