Open mtcronin99 opened 3 years ago
Hi @mtcronin99, I'm not sure that I follow. Can you explain your use case in more detail? What have you tried doing so far?
I haven't tried any thing. I will do that today. I'm trying to reconcile a couple of statements in the README.
...a common failure of the above listed alternatives is that configuration of things like a repeating schedule should be separated from code in a configuration file which an operations team (not the developers) can control.
and
calendar - [String] [optional] An option String which is the name of a configured Calendar. This Calendar is applied to this schedule as "exemptions" (Any times/dates falling in the Calendar will be excluded from the schedule firing - i.e. a Calendar that excludes all Mondays would keep a schedule configured to trigger every hour, from triggering at all on Mondays. NOTE: In versions 1.3.x and prior, this property was "calendars" and supported a list of Strings. However, Quartz, and by proxy, this library never actually supported multiple calendars for one schedule.
and finally that fact that none of the calendars configured in the configuration file have a way to specify the base
calendar.
Is there a way to chain/combine different calendar types into a single calendar? An Annual calendar by itself isn't very useful. Combined with Holiday, Weekly and other types, it makes sense.