Description
As discussed on the mailing list, I propose to introduce some kind of pluggable Bean, which would allow to control both whether the Scheduler as a whole should start, as well as to provide a hook for controlling each single task invocation.
The default implementation would always return true on both, which makes sure the default behavior is the same as it has always been. Being a Bean, it can be customized via CDI mechanisms (Specializes, Alternative, etc.).
The Bean should provide the following signature:
boolean isSchedulerEnabled();
boolean vetoJobExecution(Class<T>);
TBD:
- Provide support for multiple implementations of SchedulerControl
Better name for shouldJobBeStarted?FoundUse JobName in shouldJobBeStarted?Not needed as discussed on mailing list
Development takes place at https://github.com/j-be/deltaspike/tree/scheduler-control
Pull request can be found at https://github.com/apache/deltaspike/pull/84
Attachments
Issue Links
- is related to
-
DELTASPIKE-1449 Broken quartz annotations and duplicate job details
-
- Open
-