<?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 TOS 7.0.1 problem: build type OSGi Bundle For ESB in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376059#M144381</link>
    <description>&lt;P&gt;Hi community,&lt;/P&gt; 
&lt;P&gt;I try new version of Talend ESB - Talend ESB 7.0.1 and I find different behaviour of a building job from older version 6.1.1:&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;When I need to build a Talend Job from TOS as the "OSGI Bundle For ESB" and Job doesn't contains certain component (for example tESBConsumer/tRESTClient/tRESTRequest/tRESTResponse), the TOS doesn't build final .jar with inner structure of OSGi bundle but with structure of the "Standalone Job" build type - viz screen "Screen_problemBuild.jpg" of unzipping .jar.&lt;/P&gt; 
&lt;P&gt;If the Talend Job contains tESBConsumer (can be deactivated), final .jar is built with the OSGi structure (viz screen "Screen_correctBuild.jpg" of unzipping .jar) and this Job works in Talend ESB runtime properly.&lt;/P&gt; 
&lt;P&gt;&lt;BR /&gt;I missed something in TOS settings or Job designing? Or this is a new behaviour in new versions of Talend ESB or this is some error to be fixed?&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thank your answer&lt;/P&gt; 
&lt;P&gt;&lt;BR /&gt;Note:&lt;BR /&gt;- OS of work station: Windows 10 64bit&lt;BR /&gt;- Java version: JDK 1.8.0_181&lt;BR /&gt;- Talend ESB version: 7.0.1_SE_246_release/7.0.1&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 07:36:52 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T07:36:52Z</dc:date>
    <item>
      <title>TOS 7.0.1 problem: build type OSGi Bundle For ESB</title>
      <link>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376059#M144381</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt; 
&lt;P&gt;I try new version of Talend ESB - Talend ESB 7.0.1 and I find different behaviour of a building job from older version 6.1.1:&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;When I need to build a Talend Job from TOS as the "OSGI Bundle For ESB" and Job doesn't contains certain component (for example tESBConsumer/tRESTClient/tRESTRequest/tRESTResponse), the TOS doesn't build final .jar with inner structure of OSGi bundle but with structure of the "Standalone Job" build type - viz screen "Screen_problemBuild.jpg" of unzipping .jar.&lt;/P&gt; 
&lt;P&gt;If the Talend Job contains tESBConsumer (can be deactivated), final .jar is built with the OSGi structure (viz screen "Screen_correctBuild.jpg" of unzipping .jar) and this Job works in Talend ESB runtime properly.&lt;/P&gt; 
&lt;P&gt;&lt;BR /&gt;I missed something in TOS settings or Job designing? Or this is a new behaviour in new versions of Talend ESB or this is some error to be fixed?&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thank your answer&lt;/P&gt; 
&lt;P&gt;&lt;BR /&gt;Note:&lt;BR /&gt;- OS of work station: Windows 10 64bit&lt;BR /&gt;- Java version: JDK 1.8.0_181&lt;BR /&gt;- Talend ESB version: 7.0.1_SE_246_release/7.0.1&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 07:36:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376059#M144381</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T07:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: TOS 7.0.1 problem: build type OSGi Bundle For ESB</title>
      <link>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376060#M144382</link>
      <description>&lt;P&gt;There is a&amp;nbsp; difference between standard &amp;amp; esb jobs.&lt;/P&gt;&lt;P&gt;If you build a Job as an OSGI Bundle you need to have at-least one ESB component.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 09:26:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376060#M144382</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-09-21T09:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: TOS 7.0.1 problem: build type OSGi Bundle For ESB</title>
      <link>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376061#M144383</link>
      <description>Ok, thanks for answer</description>
      <pubDate>Fri, 21 Sep 2018 12:16:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376061#M144383</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-09-21T12:16:45Z</dc:date>
    </item>
    <item>
      <title>Re: TOS 7.0.1 problem: build type OSGi Bundle For ESB</title>
      <link>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376062#M144384</link>
      <description>&lt;P&gt;hey,&lt;/P&gt; 
&lt;P&gt;I have almost the same thing, but when build route camel with TalendJob with start tRouteInput and end tRouteOutput but the job .JAR is everytime in job standalone and not ESB Bundle.&lt;BR /&gt;&lt;BR /&gt;when ai deploy my .KAR (route.JAR and job.JAR) the job.JAR are all time job standalone and my karaf dont install because error with ressource JOB.JAR.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 14:37:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/TOS-7-0-1-problem-build-type-OSGi-Bundle-For-ESB/m-p/2376062#M144384</guid>
      <dc:creator>martel</dc:creator>
      <dc:date>2018-09-21T14:37:36Z</dc:date>
    </item>
  </channel>
</rss>

