I completely agree that implementation without a use case is not really the best way to go.
Forcing users to use an OSGi service registration to avoid calling the JRE api does not seem worthwhile either. I guess the part I'm still missing is the use cases for wrapping Timer or ScheduledExecutorService. ;-) On Mon, Jul 25, 2011 at 13:51, Andreas Pieber <anpie...@gmail.com> wrote: > I'm not sure if it's really worth to use quartz here. Still I think we > shouldn't start implementing things before there is actually a use case for > it (at least I'm happy right now with the classical timer support :)). > Quartz can also work with the new Java 6 scheduling interface --> we can > upgrade later here (and stay fully backward compatible). > > In addition I think it may be nice to add some blueprint support similar to > the spring timer support which can also work with quartz and the > java6 scheduler. In addition it would be nice to have commands to start such > services manually and to list all registered timers and the time till they > will be executed next > > WDYT? > > Kind regards, > Andreas > > On Thu, Jul 21, 2011 at 23:32, Ioannis Canellos <ioca...@gmail.com> wrote: > >> Do you think that it worths using quartz instead? >> >> >> On Friday, July 22, 2011, Guillaume Nodet <gno...@gmail.com> 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 <ioca...@gmail.com> >> 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 >> * >> > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
