Hi You dont have to use Camel routes, only if that makes sense for you. You can use Camel as a plain client and use eg producer template / consumer template to use the Camel components for easy integration with all what these components support.
On Thu, Jan 22, 2015 at 3:09 PM, Gershaw, Geoffrey A. <[email protected]> wrote: > Hello, > > A quick update to this. Would the camel approach to managing Quartz jobs > programmatically be: > > > 1. For every new job, create a new route dynamically. The quartz endpoint > would be configured dynamically by creating the option string > programmatically. Something like this: > > a. > from("quartz2://myGroup/myTimerName?trigger.repeatInterval=2&trigger.repeatCount=1").routeId("myRoute").to("mock:result") > > > > 2. To delete the job, stop/delete the route. > > > > 3. To change the job, do step 2 followed by step 1. > > > > 4. If the above is correct, I would like to send the new quartz route an > object that it will send according to the schedule. Once the quartz route has > this object, it can start firing. I don't want it firing without the object. > > > Hopefully, the above is clear. Any suggestions, would be greatly appreciated. > > > Thanks, > > > Geoffrey A Gershaw > > > > > =============================================================================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html > =============================================================================== -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
