|
From: Ivan R. <iv...@we...> - 2003-10-10 09:20:53
|
Mike Cannon-Brookes wrote: > Personally I'd like to see (or would be happy to create) a Quartz bean. And I would be happy to work with you so that schedulers coexist :) > Rewriting your own scheduler seems like a waste of effort to me? Quartz is > extremely flexible, Open Source and has been debugged for a long time! > Writing a scheduler is no easy task. I am sure it seems that way from your point of view. It is different from my point of view: it doesn't give me what I want, it forces me to think about things I don't care and it simply doesn't "feel" right. For the record, after getting suggestions from this list, I did attempt to wrap Quartz and use it from Spring. For a while I thought I'll do that but I gave up after learning more about it. In the end, I do believe that it is an overkill for most uses. It is an eternal question you are asking, to "buy or build". I am not against "buying" - I happily chose to use Spring over my own XML-based configuration mechanism because I believed it is better than anything I would be able to build. I don't think that way about Quartz. > Why not configure them all in the context file? Simply put there are often > hundreds of scheduled jobs and they more belong in their own custom file > IMHO. Both approaches have their merits. People will probably chose on or the other depending on the type of project they have. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |