Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 12993 invoked from network); 3 Sep 2003 21:07:39 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Sep 2003 21:07:39 -0000 Received: (qmail 1303 invoked by uid 500); 3 Sep 2003 21:07:07 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 1245 invoked by uid 500); 3 Sep 2003 21:07:06 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 1037 invoked from network); 3 Sep 2003 21:07:03 -0000 Received: from unknown (HELO limbo.otego.com) (195.216.81.146) by daedalus.apache.org with SMTP; 3 Sep 2003 21:07:02 -0000 Received: (qmail 4222 invoked from network); 3 Sep 2003 21:00:23 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 3 Sep 2003 21:00:23 -0000 Date: Wed, 3 Sep 2003 23:00:23 +0200 (CEST) From: Giacomo Pati Sender: giacomo@limbo.otego.com To: dev@cocoon.apache.org Subject: Re: Quartz version In-Reply-To: <1062612637.28156.114.camel@yum.ot> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wed, 3 Sep 2003, Bruno Dumon wrote: > Giacomo, > > Just saw this printend on my console: > > INFO: Quartz scheduler version: 1.0.7 > > I think you made the same mistake I did when I first tried to download > quartz: the newest versions are at the bottom of the download page: > http://sourceforge.net/project/showfiles.php?group_id=23781&release_id=84796 > > 1.2.2 seems like the most recent stable release. Uhh, sorry, didn't saw it. I'll fix that tomorrow. Anyway, could some of you review that new block and give me your oppinion about names of config elements/attributes (I'm not good in naming) and the interface JobScheduler (I know it's still missing something i.e. getJobList or alike to enable management of Jobs). The ThreadPool I've written for Quartz (well it's just a wrapper) could be refactored as a component of it's own (seems Doug Lea's utility classes are well accepted, now ;-), and it's in Cocoon anyway). BTW: Anybody written a Commons LogFactory that uses a LogKitManager? I'd like to get Quartz logging in one of our loggers. Giaomo