Then there's something wrong with the aggregator, I'd say. The result of processing is always: out if present, otherwise in. Makes sense?
I hope this helps, Hadrian On Oct 14, 2010, at 12:43 AM, ext2 wrote: > I still feel it's a bug; let's give a sample as following: > > <from uri="direct:start"> > <multicast ref="some-aggregate"> > <transform A/> > <bean B/> > <bean C/> > <multicast> > > While writing the aggregator, how does I know where the result stored, in or > out message? I can only determine it by exchange pattern; > If the route is using InOnly pattern(which is default), the aggregator will > aggregate In message of Exchange. But the transform will always return out > message as result, so the aggregate result isn't correct; > > ============================================================== > Does this [1] explain it? > Hadrian > > [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html > > > On Oct 13, 2010, at 11:51 PM, ext2 wrote: > >> The Transformer Processor always set Out Message as result and doesn't >> care what MEP being;(At least until version camel 2.4.0, it being so, > 2.5.0 >> I haven't checked) >> >> It seems doesn't confirm to the rules of camel's MEP, why? >> >> > > >
