If A, B, C, D are not related to each other and you don't need to add more control on the consumers, I don't think you need to use camel at all, you can just use quartz directly to do your job.
-- 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 Sunday, December 23, 2012 at 9:50 AM, ammamon wrote: > say I have a Job Scheduler which has 4 consumers A, B, C and D. Jobs of type > X will have to be routed to Consumer A, type Y to Consumer B and so on. > Consumers A, B, C and D are to run as independent applications without any > dependency, either locally or remotely. > > The consumers take varying times to complete their jobs, which are > subsequently routed to the Job Scheduler for aggregation. > > Clones of one of the consumers may also be needed to share its eligible > jobs. A job should however be processed only once. > > Is Content-based router the best solution for this? > > Or is there any better way to handle this? I don't require those features of > the broker like automatically switching over to another consumer (load > balancing) and such in case of a failure. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Multiple-Consumers-implementation-issue-tp5724558.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
