How stop a job with tDie but not the father job

One Star

How stop a job with tDie but not the father job

I have a job (Job1) that call a subjob (Job2) with tRunJob.
If there is a tDie in Job2, Job1 also stops.
Is it possible to have a tDie in Job2 (to trigger errors) and continue process on Job1?
In my example the tFileList iterate stops while I want to continue on other files in the list.
Employee

Re: How stop a job with tDie but not the father job

pemen, I know (Talend team knows) that you use the Java generation code, but the same question is interesting for Perl generation code users. So my answer is for Perl projects.
With TOS 2.3.0RC1, you can:
1. in the child job, set the "return code" to 0 in tDie and in the father job have "Die on child error" checked in tRunJob
Or
2. in the father job, have "Die on child error" unchecked in tRunJob
Or
3. in child job, use a tWarn instead of tDie. If tWarn is after an "On*Error" (OnComponentError or OnSubjobError) link, father job doesn't consider the child job as returning an error ("Die on child error" can be checked in father job), as described in 964
PS: pemen, in all your topics, give the following information: TOS release and project language, it makes or answers faster
One Star

Re: How stop a job with tDie but not the father job

OK will it be available in 2.3 for java components ?
The bugtracker is only for PERL and I don't see any modification for java.

Thanks
PS : OK for TOS release and project language
Employee

Re: How stop a job with tDie but not the father job

I have created feature 2813
Hope it will be in 2.3
Regards,
One Star

Re: How stop a job with tDie but not the father job

Thanks.
I hope too !