Another vote for Google RFC-2445: we've been using it in our application for over a year, no problems. It was even fairly easy to extend it to support hourly recurrences required by our domain.
Chris On Jan 30, 10:20 am, Robin <[email protected]> wrote: > by way of an update for anyone interested we went for this one: > > http://code.google.com/p/google-rfc-2445/ > > mainly because it was more lightweight and match well to our existing > implementation. things are looking pretty good so far. > > On Jan 30, 9:47 am, Robin <[email protected]> wrote: > > > Thanks to both of you suggesting quartz, We'll try it out. I also > > posted this question to stack overflow > > >http://stackoverflow.com/questions/492055/whats-the-best-java-date-re... > > > and was recommended to try this > > >http://code.google.com/p/google-rfc-2445/ > > > We'll probably give both a look so I'll let you know how it goes. > > > Robin > > > On Jan 30, 7:07 am, Wayne Fay <[email protected]> wrote: > > > > > We use quartz. Does the job for us. > > > > Another "vote" for quartz... My teams have been using it for several > > > years now in multiple applications with essentially no issues > > > whatsoever (except for human errors in configuring jobs and > > > schedules). > > > > We've contributed a few features which make our lives easier as well. > > > The codebase is simple enough to jump into when you realize you need > > > something new or if you think you found a defect. > > > > Wayne --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
