For more complex scenarios where you want durability across Camel restarts,
it could make sense to persist the message in a db, to use message queues,
correlations, etc. What not.

In most cases, this is not necessary, especially when dealing with
synchronous interactions, where the client is waiting for an immediate
answer.

The enricher EIP is more than enough for those cases.

Regards,
Raúl.
 On 9 Feb 2013 12:19, "Jan Matèrne (jhm)" <[email protected]> wrote:

> For me (as beginner) that sounds more like
> - "save the message": message store
> - "relate": correlation identifier
> Maybe "claim check" ...
>
> Jan
>
> -----Ursprüngliche Nachricht-----
> Von: Raul Kripalani [mailto:[email protected]]
> Gesendet: Samstag, 9. Februar 2013 11:37
> An: [email protected]
> Betreff: Re: building response along with request data
>
> The enricher EIP does that for you. You just worry about writing the code
> to
> merge the data from both messages.
>
> Raúl.
> On 9 Feb 2013 08:18, "kiranreddykasa" <[email protected]> wrote:
>
> >
> > Yeah but where can I can save the request message until it gets
> > processed..??
> >
> > And after saving how can co relate the request and response ??
> >
> >
> >
> > -----
> > Regards
> >
> > kiran Reddy
> > --
> > View this message in context:
> > http://camel.465427.n5.nabble.com/building-response-along-with-request
> > -data-tp5727111p5727268.html Sent from the Camel - Users mailing list
> > archive at Nabble.com.
> >
>
>

Reply via email to