RE: [Springframework-developer] Quartz support

[Ou, R. <Ro...@sa...>]

This would be actually quite useful to us too.

+1

Rong


> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of j=FCrgen h=F6ller [werk3AT]
> Sent: Wednesday, February 18, 2004 4:43 PM
> To: spr...@li...
> Subject: [Springframework-developer] Quartz support
>=20
>=20
> Everybody,
> =20
> I've revived my Quartz support classes for Spring today. They=20
> emerged from a job scheduling consulting project I did in=20
> autumn 2003. We have concrete needs for this now at werk3AT,=20
> thus the revival: It's about quite simple cron-style=20
> scheduling of application jobs.
> =20
> The basic idea is to set up a Quartz Scheduler via a=20
> SchedulerFactoryBean, also allowing to register scheduled=20
> jobs there via a <list> of <refs> to ScheduledJobDefinition=20
> beans. A ScheduledJobDefinition is just a simple combination=20
> of a Quartz JobDetail and a Quartz Trigger.
> =20
> ScheduledJobDefinition bean implementations include:
> - DefaultScheduledJobDefinition, allowing to use any=20
> implementation of Quartz' Job interface with a declaratively=20
> configured job data map and cron trigger
> - MethodInvokingJobDefinition, allowing to specify a method=20
> of a Spring-managed bean to execute as job (completely=20
> declarative, without the need for implementing a custom Job=20
> object), with a cron trigger.
> =20
> Both job definition beans can link in a separate Quartz=20
> Trigger instance instead of a cron expression;=20
> DefaultScheduledJobDefinition can also link in a separate=20
> Quartz JobDetail instance instead of a job class.
> =20
> That's all there is: A simple declarative way of using Quartz=20
> within Spring. Typically no rescheduling or the like: All=20
> schedules are set up on context startup, defined as bean=20
> definitions. Of course, you can also fetch the Scheduler=20
> instance and perform any custom scheduling, instead of using=20
> preconfigured ScheduledJobDefinition beans.
> =20
> The typical usage scenario are low-level jobs within an=20
> application, like data synchronization or storage cleanup -=20
> all predefined jobs that are just customized by an=20
> administrator. Fits nicely into Spring's application context=20
> model; most jobs will simply delegate to Spring-managed=20
> business objects.
> =20
> I expect to have this polished by the end of the week, as we=20
> need it at werk3AT quite urgently. I'd like to include this=20
> already in Spring 1.0 final, as it's just 6 pretty simple=20
> classes (yes, I know - feature freeze - never mind ;-). The=20
> main question is where to put it: I suggest=20
> "org.springframework.scheduling.quartz".
> =20
> If there are no general objections, I'll commit it by the end=20
> of this week, for review within the next week - still plenty=20
> of time before 1.0 final ;-) Looking forward to your feedback!=20
> =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=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20