Personally I like the idea presented here, Aaron. J2EE doesn't have a
nice way to schedule things, so you end up having to add something on to
do it. I've been fortunate to have applications that didn't need to
schedule much, and when I did, all I really needed was something to wake
up every once in a while and see what needs to be done.
I can certainly see the usefulness of a simple 'cron' statement. Having
spent most of the weekend trying to get a simple GBean thread to fire
messages to an MDB to do extremely simple timed pulses, I can see the
utility of having this.
Cheers.
-Neal
Aaron Mulder wrote:
I'm more looking at the case of an application that needs to run a
daily import, daily export, and monthly report. Who wants to learn a
new set of admin tools just for that? Instead of fooling with
specialized tools, just put your job classes in a JAR and deploy that
JAR along with the rest of your application. Voila! Scheduled jobs.
If you update the jobs, you can redeploy them just like any other
code.
Thanks,
Aaron
<jobs xmlns="http://geronimo.apache.org/xml/ns/plugins/quartz-0.1";>
<environment xmlns="http://geronimo.apache.org/xml/ns/deployment-1.1";>
<moduleId>
<artifactId>TestJobs</artifactId>
</moduleId>
</environment>
<job>
<job-name>Frequent Job</job-name>
<job-class>org.gplugins.quartz.jobs.TestJob</job-class>
<cron-expression>0/15 * * * * ?</cron-expression>
</job>
<job>
<job-name>Uncommon Job</job-name>
<job-class>org.gplugins.quartz.jobs.AnotherJob</job-class>
<cron-expression>0 10 10 * * ?</cron-expression>
</job>
</jobs>
