Re: OScheduler

Yes! Although the one thing that is glaringly missing from your 
description is support for multiple persistence mechanisms, so any 
objections to adding that in?

Anyway, big +1 from me for having such a component, as long as it 
follows the same principles as all the others (few dependencies, 
optional support for stuff, etc etc).

Mathias Bogaert wrote:

> Guys,
> 
> Over the last month, I've written a scheduler (like Quartz), but with much
> cleaner interfaces, based on java.util.Timer, lot of the same principals as
> XWork (Job, JobSupport, JobInvocation, interceptors, etc), using the cron
> parser from OSCache, with Hibernate as backing store for storing jobs and
> job parameters (that are set on a job having setters). Startup through a
> context listener. The documentation is a work in progress, and it's not very
> well tested (almost zero unit tests, I'm not into TDD yet).
> 
> I've been thinking about releasing it as open source, and I'm wondering if
> OpenSymphony would be interested. Offcourse any better name or other
> suggestions are appreciated.
> 
> Mathias Bogaert
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
> 



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html