Return-Path: <users-return-62120-archive-asf-public=cust-asf.ponee.io@camel.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id CFB33200B5E
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 10 Aug 2016 17:20:41 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id CE3B7160AA4; Wed, 10 Aug 2016 15:20:41 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 2173F160A8F
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 10 Aug 2016 17:20:40 +0200 (CEST)
Received: (qmail 28959 invoked by uid 500); 10 Aug 2016 15:20:40 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 28948 invoked by uid 99); 10 Aug 2016 15:20:39 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2016 15:20:39 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 7970D1A5264
	for <users@camel.apache.org>; Wed, 10 Aug 2016 15:20:39 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.286
X-Spam-Level: **
X-Spam-Status: No, score=2.286 tagged_above=-999 required=6.31
	tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972,
	URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled
Received: from mx2-lw-us.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
	with ESMTP id FUU3uwdUVtJM for <users@camel.apache.org>;
	Wed, 10 Aug 2016 15:20:37 +0000 (UTC)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
	by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 92EB45FBFC
	for <users@camel.apache.org>; Wed, 10 Aug 2016 15:20:37 +0000 (UTC)
Received: from msam.nabble.com (unknown [162.253.133.85])
	by mbob.nabble.com (Postfix) with ESMTP id 54F022E75571
	for <users@camel.apache.org>; Wed, 10 Aug 2016 07:54:53 -0700 (PDT)
Date: Wed, 10 Aug 2016 08:20:36 -0700 (MST)
From: awilliams <ashpublic@mac.com>
To: users@camel.apache.org
Message-ID: <1470842436661-5786244.post@n5.nabble.com>
In-Reply-To: <1470768956456-5786218.post@n5.nabble.com>
References: <1470768956456-5786218.post@n5.nabble.com>
Subject: Re: Chaining web service calls in a route
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Wed, 10 Aug 2016 15:20:42 -0000

I've now resolved this. The problem was that the web service consists of two
operations and for some reason when I called the producer endpoint it was
selecting the first operation by default - same parameter but different
return value.

Therefore all I had to do was to tell Camel explicitly which operation I
wanted to be called by setting the appropriate header:

    <route id="Request: Store Request">
            <from uri="cxf:bean:inboundRequest" /> (signature = "MyResponse
request(MyRequest)") 
                
            <setHeader headerName="operationName">
                <constant>execute</constant>
            </setHeader> 
        
            <to uri="cxf:bean:inboundExecute" /> (signature = "MyResults
execute(MyRequest)") 
    </route>

I'm guessing that if my web service operations would have had different
parameter types then camel/cxf would have been able to work out which one to
call without me having to explicitly tell it.

The Camel in Action is extremely light on details for interacting with the
cxf component, I wonder if anyone here has any practical advice on how to
set up routes where the operations are all from the same wsdl file? For
example I've had to make the same web service available on multiple ports
(declared multiple cxf:beans) just so that I could associate unique routes
to each operation, which doesn't feel like the right solution.



--
View this message in context: http://camel.465427.n5.nabble.com/Chaining-web-service-calls-in-a-route-tp5786218p5786244.html
Sent from the Camel - Users mailing list archive at Nabble.com.