SLF4J: Class path contains multiple SLF4J bindings

[jlolling]

SLF4J: Class path contains multiple SLF4J bindings

[jlolling]

This happens if you mix the build-in Talend JSON component tExtractFieldJSON with my JSON components.
The tRESTRequest and tRESTResponse component does not cause any problems - I do the same.

[blag001]

Hi @jlolling
I'm pretty sure we don't use any native JSON components in this job, I'll ask to be assured.

Could you share some screenshot of a basic REST web-service using tJSONDoc* ?
We probably miss something on our side if you're able to make them work together.

Best wish

--
edit

Ok, no native JSON component used.

Here is some screenshot of our tests.

[jlolling]

tug_20180215_gvl_core_webservices.pdf
I had made a presentation about creating web services with Talend DI and these JSON components.
I am sorry, this file is in German but you will get an idea about the design because of the screenshots.

[jlolling]

Could you please go to the advanced settings of the tJSONDocOpen and tell me the component version?
Please take care you do not have the build-in json components also in no other parent, child or embedded job of you current job (running within the same JVM instance).

[jlolling]

The sl4j binding problem is not the problem, the problem is the out-dated jayway library you have in your classpath of the job.

[sounajd]

Hi @jlolling

I am working with blag001 on the same Job, the tJsonDocOpen's version is 13.0, I think it is the latest version,
is there any possibility to update the Jayway Library ?

[jlolling]

Could you tell me the Talend Studio version you use please?
And it would be great to have an exported job item - if possible.
Otherwise I can offer, we meet us per skype.

[jlolling]

Your latest screenshot show only the problem with the logging. Actually this is not really a problem.
The much more dangerous problem was the wrong jayway library (Clones objects detected! Use the latest Jayway library 2.2.1+) but this is not the case in you last shown job.
My json components does not use sl4j and does not ships the log4j library. So I am pretty sure the error message from sl4j will persist if you remove my component.