On Mon, 1 Sep 2003, Bruno Dumon wrote: > On Mon, 2003-09-01 at 11:37, Giacomo Pati wrote: > > On Mon, 1 Sep 2003, Reinhard Poetz wrote: > > > > > > > > > > > On Behalf Of Giacomo Pati > > > > > > > On Mon, 1 Sep 2003, Andreas Hochsteger wrote: > > > > > > > > > Hi! > > > > > > > > > > Just in case you didn't know: > > > > > Did you have a look at the Quartz Scheduler? > > > > > http://www.part.net/quartz.html > > > > > http://www.part.net/quartz_features.html > > > > > Perhaps it already does what you need. > > > > > It's licensed under a BSD and Apache-Style license. > > > > > > > > I've seen it some time ago but thought it is quite too much > > > > for a simple cron mechanism we are discussing here. > > > > > > > > Any other thoughts? > > > > > > Do you think it is difficult to use/to integrate? From the features list > > > it is exactly what we need, isn't it? > > > > IMHO, from the feature list it is way too much we need, isn't it? > > I think many of it are optional features, and those extra features might > come in handy some day. If it does everything we need and if it's solid, > why not use it?
Hmm, the cocurrency util from Doug Lea does alot Quartz offers. So my oppinion was not to add another dependency. Quartz (if I've read the feature list correctly) doesn't offer Cron spec parsing, so we have to do it anyway. And because I've alread done this for another project some times ago I thought to but it into a Scheduler by it own (mean in the org.apache.cocoon package space). So, the scheduler I've proposed is already done. I just have to repackage it and add some more javadocs etc. It's about to be ready to be committed tomorrow. If there are still objection I hold on the commits until we reached consensus. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
