I think this should be possible. You first send the exchange to the validator, then to a static recipient list. The exchange would be send to the three lookup services and then redirected to an aggregator. It would require some codingas you would need to bridge an InOut request with an InOnly request (which is not implemented yet), and a custom aggregator. But all lookups would be executed in parallel.
That said, i may be easier to use some orchestration engine like BPEL or the BpmScript component, or even to write your own lightweight component that would do this. Cheers, Guillaume Nodet On 6/15/06, markpittsnh <[EMAIL PROTECTED]> wrote:
The business context is order processing. I want to chain together validation, and 3l lookup services. I want to find the best way to append the response from each lookup service onto the original request. Ultimately, the the xml that I have after the last lookup contains the originall request, as well as the response from each of the 3 lookups. I also want to conditionally branch to a different destination, let's say the second lookup fails (for example, customer id lookup fails, therefore customer creation is required before I can create the order). Also, I don't want to move forward if the validation service fails. I suspect the BPEL is the right choice as I cannot see how to accomplish this with eip. Thanks in advance for any suggestions. Regards, Mark -- View this message in context: http://www.nabble.com/how-to-accumulate-request-and-response-along-a-routing-t1794966.html#a4891295 Sent from the ServiceMix - User forum at Nabble.com.
