<?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: Camel route web service &amp; SOAPAction in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273252#M50294</link>
    <description>Since you mentioned SOAPAction explicitly, Camel also propagates the cxf Header.HEADER_LIST and SoapBindingContstants.SOAP_ACTION headers, so that should be available as well.</description>
    <pubDate>Mon, 13 Jun 2011 23:44:58 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2011-06-13T23:44:58Z</dc:date>
    <item>
      <title>Camel route web service &amp; SOAPAction</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273250#M50292</link>
      <description>Hi, 
&lt;BR /&gt;I want to add a new operation to the WSDL of a Camel route exposed as a web service with CXF, 
&lt;BR /&gt;and a specific route for this operation. 
&lt;BR /&gt;What I don't know is how I can differentiate request to execute the right route... 
&lt;BR /&gt;Do I have to implement a CXF SOAPAction interceptor ? Is there a native mechanism in Camel to do that ? 
&lt;BR /&gt;That's how I've declared my CXF Endpoint : 
&lt;BR /&gt; 
&lt;PRE&gt;&amp;lt;cxf:cxfEndpoint id="CXFTESBRouteService" &lt;BR /&gt;		address="/WSRouteService"&lt;BR /&gt;		serviceClass="com.talend.demo.ws_routeservice.WSRouteService"&lt;BR /&gt;		wsdlURL="classpath:WEB-INF/WS_TalendESBDemo.wsdl" /&amp;gt;&lt;/PRE&gt; 
&lt;BR /&gt;That's my (very simple) route : 
&lt;BR /&gt; 
&lt;PRE&gt;from("cxf:bean:CXFTESBRouteService").to("log:test");&lt;/PRE&gt; 
&lt;BR /&gt;Thanks !</description>
      <pubDate>Sat, 16 Nov 2024 12:52:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273250#M50292</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T12:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Camel route web service &amp; SOAPAction</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273251#M50293</link>
      <description>Hi,
&lt;BR /&gt;Looks like you're implementing a service with multiple operations. So what you are asking, I think, is what is the differentiator that would tell you on a route what operation was invoked. The answer to that is a header called "operationName".
&lt;BR /&gt;The easiest way to implement what you want would be using a content based router or, in a bit more elegant way, using a recipient list using one route/endpoint per operation, kinda like below (assuming your wsdl contract has operations named "myOperation1" and "myOperation2"):
&lt;BR /&gt;
&lt;PRE&gt;from("cxf:bean:CXFTESBRouteService")&lt;BR /&gt;  .to("log:test")&lt;BR /&gt;  .recipientList(simple("direct:${header.operationName}"));&lt;BR /&gt;from("direct:myOperation1").whatever-needs-to-be-done-for-myOperation1();&lt;BR /&gt;from("direct:myOperation2").whatever-needs-to-be-done-for-myOperation2();&lt;BR /&gt;&lt;/PRE&gt;
&lt;BR /&gt;You can see an example of the above in action in the camel-example-cxf-tomcat shipped with the distribution.
&lt;BR /&gt;I hope this helps.</description>
      <pubDate>Mon, 13 Jun 2011 23:24:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273251#M50293</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-06-13T23:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: Camel route web service &amp; SOAPAction</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273252#M50294</link>
      <description>Since you mentioned SOAPAction explicitly, Camel also propagates the cxf Header.HEADER_LIST and SoapBindingContstants.SOAP_ACTION headers, so that should be available as well.</description>
      <pubDate>Mon, 13 Jun 2011 23:44:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273252#M50294</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-06-13T23:44:58Z</dc:date>
    </item>
    <item>
      <title>Re: Camel route web service &amp; SOAPAction</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273253#M50295</link>
      <description>That's what I was looking for 
&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009MACn.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/154443iC5B8CACEF3D12C6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009MACn.png" alt="0683p000009MACn.png" /&gt;&lt;/span&gt; 
&lt;BR /&gt;Thank you Hadrian ! 
&lt;BR /&gt;Bahaaldine</description>
      <pubDate>Wed, 15 Jun 2011 08:38:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Camel-route-web-service-SOAPAction/m-p/2273253#M50295</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-06-15T08:38:15Z</dc:date>
    </item>
  </channel>
</rss>

