I suppose you use a request / response mechanism on the soap side. You would need to use the EIP async bridge which is able to convert an incoming InOut exchange to an InOnly exchange and wait for a correlated InOnly exchange to come back. So the soap consumer endpoint would target the eip async bridge, which in turn would go to splitter, the flights and hotels services, then go to an eip aggregator and back to the async bridge. The async would send back the response to the soap consumer.
On Fri, Oct 31, 2008 at 12:19 PM, Tomasz Prus <[EMAIL PROTECTED]> wrote: > hi, > > I have aggregator that aggregate messages from different providers eg. > hotels, flights .. but it aggregate all messages from several > requests. How to implement JMSCorrelationId that aggregator take > messages only for one request. We don't know when but we loose > JMSCorrelationId (seted in soap client). > > SoapClient (getPackage) -> splitter (getFlights, getHotels..) -> > aggregator (join messages from flights, hotels..) -> SoapClient > > Please help me! Our project stopped in progress because we cannot > implement aggregator. Where can i see some working example? > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
