99soft/guartz — pull request #6 by ginkel (2012-06-28 12:31:51+00:00)
Title: Optionally support repeated scheduling of the same job / trigger tuple (...

...which is required to support a persistent JobStore)

When using a persistent JobStore, just calling scheduleJob during the QuartzModule's schedule() invocation will end up getting some ugly org.quartz.ObjectAlreadyExistsExceptions. This change extends the JobSchedulerBuilder DSL to declaratively request to update an existing trigger (with the same key) when scheduling the job instead of bailing out.

Test case included.