Hi Steve,
and how does the starting point react on the exchange it receives
from
the end? What if the end produces multiple exchanges?
Steve Huston <shus...@riverace.com> writes:
I have also found it a bit difficult to get a straight answer on
this but my understanding at this point is that if the exchange
gets to the end of the route and is an InOut, the Out from the
last endpoint goes back to the 'from' starting point.
http://camel.apache.org/request-reply.html
-Steve
-----Original Message-----
From: Peter Nagy (Jr) <pn...@gratex.com>
Sent: Friday, December 14, 2018 10:27 AM
To: users@camel.apache.org
Subject: understanding InOut
I still don't quite grok how InOut works. When I set the
exchange pattern to
InOut, what exactly will happen? Will the *next* processor
reply to the
previous one? If so, how? If so, how does the previous
processor act on the
reply? Or is the InOut just about 1 Processor? If so, can e.g.
a Processor block
until a split is reaggregated?
I'm trying to find some documentation on this that would
explain these
details but I didn't find much. The request-reply page is brief
and uses mocks.
As a real world bonus - I'm running a mongodb aggregation
pipeline splitting
and streaming and would need to fire just 1 exchange further
down the
route when the whole aggregation is finished. I'm doing
.to("mongodb3://...")
.split(..).streaming()
...
.aggregate(..)
.hereINeed1exchange;
I recently found out that split can take an aggregator as
argument, would that
solve this case? How exactly does that work?
--
To reach a goal one has to enjoy the journey.
--
To reach a goal one has to enjoy the journey.
