There is a jira created for this issue and it will be fixed in the next release. Until then you need to patch it yourself.
Search the forum or jira and you will find the patch. // Pontus Send from my phone On Aug 1, 2012 12:34 AM, "Lance Walton" <lancewal...@mac.com> wrote: > Hi. > > I've given this a try, and with a bit of fiddling, it seems to work. Thank > you. > > Now the next challenge... > > I sometimes need to remove the route from the camel context and re-add it > with different properties. When I try to re-add it, I get an > ObjectAlreadyExistsException because a job already exists in quartz's > RAMJobStore with an id clearly derived from the route's id. How can I get > the quartz jobs cleaned up when I remove the route? > > Regards, > > Lance > _________________ > > http://www.stateofflow.com > http://www.casualmiracles.com > http://www.twitter.com/lancewalton > +44 (0)7779 026533 > > On 31 Jul 2012, at 20:10, tnk wrote: > > > Hi, > > you can try using cron scheduled route policy > > (http://camel.apache.org/cronscheduledroutepolicy.html) > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Scheduled-FTP-download-tp5716638p5716639.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > >
