camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Burkard <sburk...@gmail.com>
Subject Re: Camel route exchange intermediate call
Date Tue, 10 Dec 2013 15:30:15 GMT
Hi

You could simply save the original body into a Camel exchange-property
before it is modified. Later you can get the original body from the
property and set it into the body. But this works only if your exchange
does not get lost during processing (for example if you have a queue
inbetween).

Pseudo route code:

// save message body to exchange property to restore it later
.setProperty(SAVE_BODY, body())
... do other things ...
// restore original message body
.setBody(property(SAVE_BODY))
...continue with route ...

Cheers
Stephan


On Tue, Dec 10, 2013 at 3:26 PM, sdelanghe <stefaan.delanghe@yandex.com>wrote:

> Hey everyone,
>
> I have an web service endpoint. This message i need to keep. Before
> actually
> passing this message on to the next component i need to call another web
> service which changes the message entirely.
> Looks as i lost my entire first message (body).
>
> How can i keep my endpoint body while executing another route?
> Is there an EIP pattern for this or do i need to duplicate the exchange?
>
>
> Grtz
> Stefaan
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-route-exchange-intermediate-call-tp5744569.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message