Oct 11th, 2010, 09:04 AM
Quartz vs Spring task scheduler
We're working on a project that requires jobs to be scheduled from a web interface. So far we've got a job working fine, using the SimpleJobLauncher and SimpleAsyncTaskExecutor, passing some parameters to the job entered from the web page.
The next step is to schedule these executions - initially just from the user entering a cron expression on the input page and we're looking at using the Spring 3.0 TaskScheduler implementations vs the provided Quartz beans.
Can anyone give any pros/cons of the above? One requirement that I can't obviously see if either fulfill is persistence. If I schedule a job for tomorrow morning and there's a server re-start inbetween, my web app has no (inbuilt) way of reading it's state and starting the job correctly.