<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Global Try/Catch in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231180#M21565</link>
    <description>There are many ways to accomplish your goals, but I found the best way to tackle the issues your seeing is:&lt;BR /&gt;1. Click on code to expand it in the left pane (repository).&lt;BR /&gt;2. On routines right click create&lt;BR /&gt;3. Create your custom routines with a try catch, then start using it in your tMap&lt;BR /&gt;----------&lt;BR /&gt;Then make a tLogRow, rightclick on a tMap and choose row -&amp;gt; rejects and then click on the tLogRow. You can choose how you want to deal with these later, but the best practical method in my mind is to:&lt;BR /&gt;Create a tAssetCatcher linked to a tMap which is linked to a database table input object. Do the mapping in the tMap and now you have the error results going to a database table.</description>
    <pubDate>Wed, 10 Oct 2012 18:33:23 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2012-10-10T18:33:23Z</dc:date>
    <item>
      <title>Global Try/Catch</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231179#M21564</link>
      <description>Hello, &lt;BR /&gt;I would ask if there's a way to put a global try/catch to be sure that job will not crash and we can (eventually) display the error later (maybe just put it in the global map). &lt;BR /&gt;Is it possible a new component to be created, which would put/generate (for example) try/catch in runJobInTOS method?&lt;BR /&gt;Thank you,&lt;BR /&gt;Kostadin</description>
      <pubDate>Wed, 10 Oct 2012 16:54:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231179#M21564</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-10T16:54:34Z</dc:date>
    </item>
    <item>
      <title>Re: Global Try/Catch</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231180#M21565</link>
      <description>There are many ways to accomplish your goals, but I found the best way to tackle the issues your seeing is:&lt;BR /&gt;1. Click on code to expand it in the left pane (repository).&lt;BR /&gt;2. On routines right click create&lt;BR /&gt;3. Create your custom routines with a try catch, then start using it in your tMap&lt;BR /&gt;----------&lt;BR /&gt;Then make a tLogRow, rightclick on a tMap and choose row -&amp;gt; rejects and then click on the tLogRow. You can choose how you want to deal with these later, but the best practical method in my mind is to:&lt;BR /&gt;Create a tAssetCatcher linked to a tMap which is linked to a database table input object. Do the mapping in the tMap and now you have the error results going to a database table.</description>
      <pubDate>Wed, 10 Oct 2012 18:33:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231180#M21565</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-10T18:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Global Try/Catch</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231181#M21566</link>
      <description>If you use your job as an embedded job, in this case you can specify if the main job should fail or not if the mebedded job fails.</description>
      <pubDate>Wed, 10 Oct 2012 23:08:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231181#M21566</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-10T23:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: Global Try/Catch</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231182#M21567</link>
      <description>Thank you for your answers.&lt;BR /&gt;We use the job as a subjob, but the problem is that our process should not ends when the subjob crashes. That's why uncheck of "Die on child error" doesn't work.&lt;BR /&gt;However I found something that worked for me: tRunJob---&amp;gt;tJavaRow and the code is something like:&lt;BR /&gt;if (childJob_tRunJob_1.getException() == null) {&lt;BR /&gt;...} else {...}&lt;BR /&gt;I found that when the the subjob crash doesn't ends the process ("Die on child error" - unchecked) getException() returns the exception and in a non-crash case it's just null.</description>
      <pubDate>Fri, 12 Oct 2012 10:50:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Global-Try-Catch/m-p/2231182#M21567</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-12T10:50:22Z</dc:date>
    </item>
  </channel>
</rss>

