I'm building an app that runs some task periodically and this schedule is defined in database. I'm looking to Spring/Hibernate/Quartz technology stack to save data about quartz jobs in database.
But I heard that Quartz it pretty old, and I don't know if this combination is good for this task. Could you please suggest how to build the app, to make it possible to change schedule by direct editing of database?
Yep, Quartz is pretty old, but that's a good thing. It's proven technology that has a lot of history behind it and is still actively maintained. Although it's possible to change scheduling behavior by directly "hacking" the records in Quartz' database tables, I wouldn't do that. If you look at the cookbook there are plenty of examples of listing and updating jobs and triggers through the Java API, which you could expose as a webpage or -service.
Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.
Bring me the box labeled "thinking cap" ... and then read this tiny ad: