wrap msg with scheduledFireTime
Base trait, in case we decide to diversify down the road and allow users to pick "types" of jobs, we still want strict control over them monkeying around in ways that exposes the "bad" parts of Quartz – such as persisted mutable state
Note that this extension will only be instantiated *once* *per actor system*.
Utility classes around the creation and configuration of Quartz Calendars.
Utility classes around the creation and configuration of Quartz Calendars. All dates must be ISO-8601 compliant.
This is really about triggers - as the "job" is roughly defined in the code that refers to the trigger.
This is really about triggers - as the "job" is roughly defined in the code that refers to the trigger.
I call them Schedules to get people not thinking about Quartz in Quartz terms (mutable jobs, persistent state)
All jobs "start" immediately.