Ok i understood. Whether there is any way to merge all inout messages through aggreagtor as i know aggregate will allow only inonly messages to aggreagte.
gnodet wrote: > > Currently, the aggregator create a message containing all the received > messages. > There is no specific fault handling mechanism. > > On Thu, Feb 28, 2008 at 11:14 AM, sachin2008 <[EMAIL PROTECTED]> wrote: >> >> Thanks for the reply.... >> >> But i have a doubt in the fault handling part in aggregator.How >> aggregator >> will select only messages which is not having fault for aggregation. >> >> Whether there is any property in the aggregator. >> >> >> >> >> gnodet wrote: >> > >> > If tehre is a fault in echo1 component, the routing slip will be >> aborted >> > and >> > the fault will be sent back to the consumer, so echo2 won't receive >> it. >> > A possible way would be to use the faultsTarget of the EIP pipeline to >> > redirect faults somewhere else for a different processing. >> > In any case, the aggregator must either receive faults, recognize them >> > and process them as needed, or should timeout when all the messages >> > are not received and send a fault itself. The first solution would be >> > better. >> > >> > On Thu, Feb 28, 2008 at 9:37 AM, sachin2008 <[EMAIL PROTECTED]> >> wrote: >> >> >> >> Hi, >> >> >> >> How to handle faults in case of EIP component.. >> >> >> >> Let's suppose if we will teke static routing slip. >> >> >> >> <eip:static-routing-slip service="replaceMe:routingSlip" >> >> endpoint="endpoint"> >> >> <eip:targets> >> >> <eip:exchange-target service="replaceMe:echo1" /> >> >> <eip:exchange-target service="replaceMe:echo2" /> >> >> </eip:targets> >> >> </eip:static-routing-slip> >> >> >> >> In this routing slip will forward an inout message to >> replaceME:echo1 >> >> and >> >> then from replaceME:echo1 message will route to replaceMe:echo2. >> >> If there is any fault message will return from replaceMe:echo1 to >> >> replaceMe:echo2 then how we can handle these type of faults. >> >> >> >> >> >> Now let's consider we are using aggregator for aggregate the >> messages >> >> coming >> >> from different components. If there is any fault occured in any of >> the >> >> component then aggregator how it handles the fault before >> aggregating >> >> all >> >> the messages. >> >> >> >> >> >> Can anyone please put light on this fault handling >> >> >> >> ----- >> >> Cheers >> >> Praveen Oruganti >> >> "Think before you act and act on what you believe" >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Reg%3AFault-Handling-tp15731923s12049p15731923.html >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > ------------------------ >> > Blog: http://gnodet.blogspot.com/ >> > >> > >> >> >> ----- >> Cheers >> Praveen Oruganti >> "Think before you act and act on what you believe" >> -- >> View this message in context: >> http://www.nabble.com/Reg%3AFault-Handling-tp15731923s12049p15733465.html >> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > ----- Cheers Praveen Oruganti "Think before you act and act on what you believe" -- View this message in context: http://www.nabble.com/Reg%3AFault-Handling-tp15731923s12049p15733571.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
