I think split the route into two route could be a better solution. In this way you can get the full control of how and when put the messages into the DB.
-- Willem Jiang Red Hat, Inc. Web: 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 February 13, 2014 at 9:25:56 AM, eswar (easwaramoor...@gmail.com) wrote: > > Thanks Andrzej, I think asynchronous delayer could be an option, > will try > that. And yes Queues would be an overhead here. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Resume-an-Endpoint-in-a-Route-tp5747151p5747213.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
