The good thing is: there is no standard, so you are really free to decide. That´s a huge plus for Camel. Other engines require you to run a 1 gig application server to move a few files around. The bad thing is: there is no standard, so you have to decide :-)
My favourite way is to run servicemix (as a service/daemon) and let the routes run in it forever. I really try to avoid time-based routes wherever I can, as they tend to make things less robust/messy in case of downtimes. But sometimes you have to use timer/quartz or the like for good reasons. Just my 0.02 EUR Am 29.11.2013 um 04:47 schrieb richie.rivi...@gmail.com: > Yes your right letting cron right files out is not very nice. I'm not sure > about quartz because we didn't really want the application to live. The > original idea for us what to just startup our camel app when the routes > needed to run. I would have been fine if I only had a single route in my > application however with multiple routs what options do I have? > > Is the standard out there for the camel application to live for the entire > day and for jobs to be scheduled via quartz? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Execute-a-spedific-route-from-unix-cron-tp5744010p5744060.html > Sent from the Camel - Users mailing list archive at Nabble.com.
