OK, cool. Glad that worked for you. I usually use a header simply because
it passes from route to route while the properties do not.
But in this case, the use of the properties is probably better since you
don't need the property to go anywhere else. But glad you got it working.
On Thu, Sep 29, 2016 at 11:00 PM, Shabin5785 <sha...@outlook.com> wrote:
> OK got it.. I added it as a property on exchange.
>
>
>
> Ranx wrote
> > There are a number of ways but perhaps the simplest would be something
> > like:
> >
> > .setHeader("customerId","${body.id}")
> >
> > right before the marshaling. Then in the http statement where the ID
> goes
> > you can fish it out of the header with something like
> > ${header.customerId}.
> >
> > I wrote all that free hand just now with out using an IDE so be
> suspicious
> > of the specifics but comfortable with the general approach.
> >
> > On Wed, Sep 28, 2016 at 11:35 PM, Shabin5785 <
>
> > shabin@
>
> > > wrote:
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Parse-Json-inside-RecipientList-tp5788162p5788225.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
