That of course, if you want to use Spring on your application. Why
introduce another dependency for something so simple as creating a
singleton? Besides then you will have to keep/maintain another XML file.
Ernesto
Michael O'Cleirigh wrote:
> Hello,
>
> Spring ships with a FactoryBean for the Sch
e.org
Subject: Re: Integrating Scheduler into Web Application
Hi Will,
Maybe this is more question for the quartz mailing list
Probably you would want to have only one scheduler per application, so
you should follow a singleton pattern. E.g.
public class SchedulerLocator {
private s
Hello,
Spring ships with a FactoryBean for the Scheduler
see
http://static.springframework.org/spring/docs/2.5.x/reference/scheduling.html#scheduling-quartz
I guess it depends on the persistence strategy your jobs have but it
could be as easy as injecting the spring managed scheduler bean
int
Hi Will,
Maybe this is more question for the quartz mailing list
Probably you would want to have only one scheduler per application, so
you should follow a singleton pattern. E.g.
public class SchedulerLocator {
private static Scheduler scheduler;
public static Scheduler getS
whatsoever, just to point me in the right direction, would be much
appreciated.
Thanks
Will
--
View this message in context:
http://www.nabble.com/Integrating-Scheduler-into-Web-Application-tp20960629p20960629.html
Sent from the Wicket - User mailing list a
