Hello Deb

1)I remembered there was a related bug on TOS3.0.X, please download the latest version and try again.
2)Change the main link to iterate link out of tWaitForFile.

Best regards

          shong

Hello

do I just install and then import my exported projects (or can I just open them in the new release)?

You only need install the latest release and then import the exist projects.

Best regards

          shong

Hi Shong (or anyone),

Do you know if this is a bug that the child job jar is not present in the parent jar, or is there something I'm doing wrong when I package?  It's getting annoying copying the child jar every time I package to test on the server.

Thanks for the help.
Regards,
-Deb

Hi Paul,

Thanks for the reply.  I wish that was it.  I didn't have spaces or dashes, but I had underlines and period, so I tried removing them.  But I'm still having the same problem.  It's not creating the child jars correctly.  And I'm not sure that copying the jars from the exported children is working right either because I'm having trouble getting the child to use the correct context variables.  Do you know if it is kosher to just copy the jar from the packaged child into the parent, or is there more to solving the issue by hand?

Thanks again for the help.
Regards,
-Deb

UPDATE:  My job is working now with context variables - I had to change the children to use the same context group as the parent and now it works.  Still having the problem of the child jars not being created properly though.....

Last edited by DebAtNethealth (2009-08-25 15:29:10)

Hi,

I am experiencing this problem as well.  I have opened a BugTracker issue and a help ticket with Talend support, but I am not getting any traction on the issue.  This is a very serious flaw in Talend and affects not only generation through the Administration center, but also generation of the job when executing through distant run.  I am shocked that this old thread does not have one helpful post from a Talend Engineer.  I am using the same workaround you have described, but when you have a job with dozens of child jobs, it is quite painful to manually generate the JAR for each of the child jobs and then manually copy those JARs into the proper directory on the job server anytime a change is made and needs to be deployed.

This is simply unacceptable as a user who is paying to use the Talend Integration Suite.  Can Shong or someone from Talend verify that this is a bug that is actively being worked on?  If not, I haven't received one suggestion as to what we might be doing wrong that would cause these JARs not to be generated.  I have received suggestions to make sure to check the box for 'transmit whole context' in each of the tRunJob components, which doesn't solve the issue. 

I am using TIS 3.2.1 and it appears this problem continues to persist.  I know it's a shot in the dark, but I'm hoping that by bumping this thread someone out there may know the solution.