tRunJob: Separate tRESTRequest and tRESTResponse in parent/child jobs
Hi, I have a job that contains one tRESTRequest and, depending on conditions, the flow can redirect to different tRESTResponses The job works well and I would now like to have the many tRESTResponses in different child jobs (just for a cleaner screen) Context variables are passed to the child job which can be seen in the console by using System.out.println(context.serviceMessage); in a tJava When the flow gets to the tRESTResponse within the child job, I get the following message: [center][color=#ff3333][WARN] nonsense: tRESTResponse component used without tRESTRequest component on the job[/color]
[/center] Is there a setting in the tRunJob component that could link the tRESTResponse of the child job to the tRESTRequest of the parent job? If not, is there a way to separate a tRESTResponse and a tRESTRequest in parent/child jobs?
This is not possible. The tRestRequest must be paired with a tRestResponse within the same job. However, you can make your job look cleaner by carrying out the processing in a child job and passing out the response message to the parent job using a tBufferOutput. This would then be connected to a tRestResponse component.
@rhall_2.0 : This is exactly what I also prefer as design. It has a lot advantages with testing the jobs and give us the possibility to reuse the job also for other purposes.
