Re: [Springframework-developer] Quartz support

[Mike Cannon-B. <mi...@at...>]

Woo! Good work! :)

It will allow us to get rid of Atlassian Scheduler - basically just a simpl=
e
wrapper around Quartz with a simple file for configuration of jobs and
triggers. (sample config file attached if anyone's interested)

Does yours do all that? (simple setup of job classes, cron and simple
triggers etc)

(I'm sure it can - just checking)

Cheers,
Mike
=20
On 19/2/04 9:43 AM, "j=FCrgen h=F6ller [werk3AT]" (jue...@we...)
penned the words:

> Everybody,
>=20
> I've revived my Quartz support classes for Spring today. They emerged fro=
m a
> job scheduling consulting project I did in autumn 2003. We have concrete =
needs
> for this now at werk3AT, thus the revival: It's about quite simple cron-s=
tyle
> scheduling of application jobs.
>=20
> The basic idea is to set up a Quartz Scheduler via a SchedulerFactoryBean=
,
> also allowing to register scheduled jobs there via a <list> of <refs> to
> ScheduledJobDefinition beans. A ScheduledJobDefinition is just a simple
> combination of a Quartz JobDetail and a Quartz Trigger.
>=20
> ScheduledJobDefinition bean implementations include:
> - DefaultScheduledJobDefinition, allowing to use any implementation of Qu=
artz'
> Job interface with a declaratively configured job data map and cron trigg=
er
> - MethodInvokingJobDefinition, allowing to specify a method of a
> Spring-managed bean to execute as job (completely declarative, without th=
e
> need for implementing a custom Job object), with a cron trigger.
>=20
> Both job definition beans can link in a separate Quartz Trigger instance
> instead of a cron expression; DefaultScheduledJobDefinition can also link=
 in a
> separate Quartz JobDetail instance instead of a job class.
>=20
> That's all there is: A simple declarative way of using Quartz within Spri=
ng.
> Typically no rescheduling or the like: All schedules are set up on contex=
t
> startup, defined as bean definitions. Of course, you can also fetch the
> Scheduler instance and perform any custom scheduling, instead of using
> preconfigured ScheduledJobDefinition beans.
>=20
> The typical usage scenario are low-level jobs within an application, like=
 data
> synchronization or storage cleanup - all predefined jobs that are just
> customized by an administrator. Fits nicely into Spring's application con=
text
> model; most jobs will simply delegate to Spring-managed business objects.
>=20
> I expect to have this polished by the end of the week, as we need it at
> werk3AT quite urgently. I'd like to include this already in Spring 1.0 fi=
nal,
> as it's just 6 pretty simple classes (yes, I know - feature freeze - neve=
r
> mind ;-). The main question is where to put it: I suggest
> "org.springframework.scheduling.quartz".
>=20
> If there are no general objections, I'll commit it by the end of this wee=
k,
> for review within the next week - still plenty of time before 1.0 final ;=
-)
> Looking forward to your feedback!
>=20
> Juergen
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=CCk
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer