I don't know if this will work for you.
But using only EIP i could think of using a static routing slip that
will route first to SE1, after SE1, it will route to a series of content
based router-SE pair.
Each CBR will check the message for a flag that will determine if the
exchange will be sent to the SE or not.
Consumer <-> Static Routing Slip <-> SE 1 (if condition is met set flag
to true in message)
<-> CBR (check if flag
is true) <-> SE2
<-> CBR (check if flag
is true) <-> SE3
I'm sure there are more and better ways to achieve this, but this is the
only one I can think of now. :-)
Hope it helps.
csturtz wrote:
Question: is it possible to use nested rules, and one of those rules end the
routing chain and return to the original consumer?
Here's what i need:
1. I always want to start out going to ServiceEngine1
2. After SE1, if a condition is met, go to ServiceEngine2
else, return to consumer
3. After SE2, if a condition is met, go to SE3
else, return to consumer
4. After SE3, if a condition is met, go to ServiceEngine4
else, return to consumer
Thanks!
chad
