Do you think that it worths using quartz instead?
On Friday, July 22, 2011, Guillaume Nodet <[email protected]> wrote: > Well, honestly, I'm not sure it's really worth the pain if the goal is > simply to avoid using > Executors.newSingleThreadScheduledExecutor().schedule(runnable, > delay, TimeUnit.MILLISECONDS) > > If there's a need to manage recurrent tasks, we need to have a full > featured engine for that and have a much better support for it. > > Just my $0.02 > > On Thu, Jul 21, 2011 at 15:38, Ioannis Canellos <[email protected]> wrote: >>> >>> >>> The JDK Timer is kinda @deprecated in favor of the >>> ScheduledExecutorService in Java5+. >>> The latter supports thread pooling. >> >> >> Thanks Claus for bringing this up. For me this is enough. If you think that >> we should still use quartz to take advantage of features like persistence, >> clustering etc, let me know. >> >> >> -- >> *Ioannis Canellos* >> * >> http://iocanel.blogspot.com >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> Apache ServiceMix <http://servicemix.apache.org/> Committer >> * >> > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer *
