This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
How about just running the job every weekday (since this is an easy schedule to set up in quartz), and having the first step of the job be to check against the database whether it should run the rest of the job or not?
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Joined: Apr 04, 2004
Nathan, You are right and it is one of the solutions that we have. I am researching if I can run the jobs only on non-holidays as I mentioned above with holiday(s) list in DB without having to do manual/code check in the scheduled job.