Context variables when deploying OSGI bundle for tRESTrequest component

[MBroto]

Hi all.

I created this very simple job which basically imports a ssh certificate, performs a connection to an endpoint and returns this response. Running from local dev env works fine but when deploying to ESB runtime, gives me this exception (just at launch time):

java.lang.RuntimeException: request is not provided

    at aytohuesca.test_0_1.test.tRESTRequest_1_LoopProcess(test.java:1697)

    at aytohuesca.test_0_1.test.tSetKeystore_1Process(test.java:1007)

    at aytohuesca.test_0_1.test.runJobInTOS(test.java:2989)

    at org.talend.esb.job.controller.internal.SimpleJobTask$JobRunner.run(SimpleJobTask.java:81)

    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

    at org.talend.esb.job.controller.internal.SimpleJobTask.run(SimpleJobTask.java:63)

    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

    at java.base/java.lang.Thread.run(Thread.java:834)

I have my job like that:

Hi have a host+port in context.endpoint but nevertheless I overrode it in /etc/test.cfg and works fine (the override), because at start, message component shows it properly:

But, I cannot navigate to the resource http://localhost:8040/rss

I tried specifying in cfg file host, port... but didn't work neither (http://localhost:8040/rss,

http://localhost:8088...

)

If I run it from Studio, it deploys properly in the desired url (set from context), but I have been completely unable to deploy it from karaf and furthermore, I have this exception that I suspect has to do with the probem of karaf not setting up the endpoint.

Anyone that could help, please?

Thanks in advance!

[MBroto]

From the docu...

https://help.talend.com/reader/jomWd_GKqAmTZviwG_oxHQ/X3E76BTSITWdHqP_IJ1UxQ

It was not a context variable what I was using but a configuration variable... nevertheless, if the behaviour is that this cfg variables override the context ones... obviously is not going to work in runtime. A pity because it's quite anoying to have to hardcode endpoints.