Re: Is there any way to 'park' values for later use

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

Re: Is there any way to 'park' values for later use

Hi, I Had a similar problem like that. I think that you need to look in into "Claim Check" pattern http://camel.apache.org/claim-check.html Regards, Ismail On Wed, Jun 29, 2011 at 7:12 AM, Jim Talbut-2 [via Camel] < ml-node+4534068-1741869265-45...@n5.nabble.com> wrote: > Hi, > > I want to pro

Re: Is there any way to 'park' values for later use

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

Re: Is there any way to 'park' values for later use

in terms of patterns, this is the http://camel.apache.org/claim-check.html claim check and is implemented via custom processors and headers (as ychawla eluded to)... Jim Talbut-2 wrote: > > Hi, > > I want to provide a single web service that makes calls to two separate > web services. > The

Re: Is there any way to 'park' values for later use

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.