The filter and content enricher works with InOnly mep, the content based router should work with any mep. Btw, when the InOnly is supported, RobustInOnly is too.
On Wed, Mar 5, 2008 at 5:24 AM, sachin2008 <[EMAIL PROTECTED]> wrote: > > Hi, > > I am giving a list of patterns : > > wiretap: It can handle all the four MEPs and sends only inOnly message to > the listener. > static recipient list: it will forward only inonly MEPs to multiple > recipients at a time. > static routing slip: it will forward an inout message in sequence fashion. > content based router: ? > content enricher: ? > pipeline:bridges gap between the inonly and inout meps. > Message Filter : ? > xpath spltter:inonly > split aggregator:inonly > > > Can any one please modify if there is any mistake in handling MEPs for > different patterns > > ----- > Cheers > Praveen Oruganti > "Think before you act and act on what you believe" > -- > View this message in context: > http://www.nabble.com/reg%3A-handling-MEPs-tp15843000s12049p15843000.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
