Use of tRouteOutput in a DI job called from a cTalendJob
Hi
Wondering on the recommended use of this component in terms of Exchange Message Headers and Body.
Given the following scenario:
A simple route with one cTalendJob that has a tRouteInput and tRouteOutput.
I can list all the headers and body going in in the tRouteInput to make them available in a DI component.
Re the tRouteOutput I was under the impression, from some other Talend Routes I've seen, that the tRouteOutput must have at least all the same headers and body of the message listed, as if the tRouteOutput was almost responsible for completely "rebuilding" the message for the rest of the route.
However, on experimentation, I can see that this is not the case. If I omit headers or the body, the Exchange Message contains all that went into the cTalendJob, and all that was expected when the route continues after the cTalendJob.
I **can** add **New** headers and/or overwrite header values using the tRouteOutput but I am not required to list all the headers and body as said above. In fact Talend seems to require only one item in the tRouteOutput schema, and will still run with a warning even if I delete all headers and body.
I was wondering what the recommended purpose/usage of tRouteOutput is? Is it only for *manipulating* the Exchange Message?
