Hi,
I'm afraid that you have to store the parameter for second service to
use into the exchange.
Maybe you can consider to use the setProperty("header", simple(xxx));
On 6/29/11 12:11 PM, Jim Talbut wrote:
Hi,
I want to provide a single web service that makes calls to two separate
web service
il, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Is-there-any-way-to-park-values-for-later-use-tp4534068p4534068.html
> To start a new topic under Camel - Users, email
> ml-node+465428-424999138-45...@n5.nabble.com
>
You can store custom values as properties on the Camel Exchange.
On Wed, Jun 29, 2011 at 6:11 AM, Jim Talbut wrote:
> Hi,
>
> I want to provide a single web service that makes calls to two separate web
> services.
> The arguments for the two services are different and some of them are
> independe
he exchange, but I'd like to know whether
> there is any way to do it without custom processors.
>
> Thanks
>
> Jim
>
-
Ben O'Day
IT Consultant -http://consulting-notes.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Is-there-any-way-t
Can you store the values in message Headers?
--
View this message in context:
http://camel.465427.n5.nabble.com/Is-there-any-way-to-park-values-for-later-use-tp4534068p4534096.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I want to provide a single web service that makes calls to two separate
web services.
The arguments for the two services are different and some of them are
independent, so the service I offer will have a combined argument list,
and I need to do a couple of transformations to generate the a
