|
From: Ivan R. <iv...@we...> - 2003-09-12 14:33:55
|
Colin Sampaleanu wrote: > Why not just take advantage of Quartz? It's free, and has an Apache/BSD > style license. > http://www.part.net/quartz.html > http://www.part.net/quartz_features.html I reviewed Quartz for my project before I decided to wrap my own, and decided against it because it was simply too complex and too intrusive for my taste (and it didn't have/does not have file system persistence). I don't think there is anything wrong with it (besides, I did not program in it I just read the documentation). My friend used to say "Never use a cannon to accomplish what you could with a stick". > We've been using it for a while with good results. Personally, I don't > think it's a great idea to add functionality to Spring which duplicates > existing projects that are out there and that have open licenses, > _unless_ the Spring implementation has some clear advantages. Agreed. > In this > respect, maybe what makes sense is some classes to integrate Quartz into > Spring... I don't think there's an easy way to bring Quartz to Spring because Quartz requires you to implement a particular interface and go with its triggers. Also, it has its own events. But I don't want this to turn into a "battle" about Quartz. I plan to approach this issue from a point of view of Spring, make a list of functionality we may need (which will be easy since I am doing a project where this functionality will be required). Only after that we can discuss whether an existing package can be integrated. Or, perhaps, implementations could be pluggable. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |