I'm not sure why do you want to implement this kind of feature, may be you can do it by implement a custom ExcutorService and set the ExcutorService to the Splitter.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Friday, March 15, 2013 at 2:09 AM, Edwin wrote: > Hi Folks, > > I have a route using a Splitter with parallel processing enabled. The > exchange contains List<SomeObject> someObjectList and the size of > someObjectList is five. > > SomeObject contains a property - *id* If the first two elements of the list > contain the same id, is it possible to process these on the same thread > (i.e. these two elements are sticky to a certain thread) while the other > three elements are processed on separete threads? > > Any insights are much appreciated. > > Thanks, > Edwin > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Question-on-Splitter-Parallel-Processing-tp5729204.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
