<?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: Building the job as Axis webservice in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229325#M20296</link>
    <description>There is a native application called Runtime used to deploy the services, the services created with Talend ESB are not designed to run on Tomcat server.
&lt;BR /&gt;BR
&lt;BR /&gt;Shong</description>
    <pubDate>Sat, 28 Mar 2015 02:48:49 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-03-28T02:48:49Z</dc:date>
    <item>
      <title>Building the job as Axis webservice</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229322#M20293</link>
      <description>Hi , I'm currently building the job as Axis webservice. So far, the service is good to accept the string arguments. 
&lt;BR /&gt;Now I've a requirement to accept the XML content as a part of soap request.&amp;nbsp;The XML content would be around 300 - 500 KB. 
&lt;BR /&gt;I'm not sure if I can use "context_param" in this case. Please suggest me the best of doing this in talend. 
&lt;BR /&gt;Thanks, 
&lt;BR /&gt;Srinivas N</description>
      <pubDate>Thu, 26 Mar 2015 20:20:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229322#M20293</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-26T20:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Building the job as Axis webservice</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229323#M20294</link>
      <description>Hi&amp;nbsp; 
&lt;BR /&gt;With Talend Data Integration product, you can build the job as Axis webservice, pass a XML string as parameter to the web service, use a tExtractXMLFields to extract data from the XML string in the job. Talend open studio for ESB is a special product for building the web services, including SOAP web servcie and Rest web service, it allows you to build the web service to accept XML, json or other contents. 
&lt;BR /&gt;Best regards 
&lt;BR /&gt;Shong</description>
      <pubDate>Fri, 27 Mar 2015 04:13:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229323#M20294</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-27T04:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: Building the job as Axis webservice</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229324#M20295</link>
      <description>Thanks for your response.&lt;BR /&gt;Using Talend ESB , Can I write SOAP/REST Services that can run on tomcat Server instead of talend native method ?</description>
      <pubDate>Fri, 27 Mar 2015 15:04:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229324#M20295</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-27T15:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: Building the job as Axis webservice</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229325#M20296</link>
      <description>There is a native application called Runtime used to deploy the services, the services created with Talend ESB are not designed to run on Tomcat server.
&lt;BR /&gt;BR
&lt;BR /&gt;Shong</description>
      <pubDate>Sat, 28 Mar 2015 02:48:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Building-the-job-as-Axis-webservice/m-p/2229325#M20296</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-28T02:48:49Z</dc:date>
    </item>
  </channel>
</rss>

