[ https://issues.apache.org/jira/browse/DELTASPIKE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794580#comment-16794580 ]
ASF subversion and git services commented on DELTASPIKE-1369: ------------------------------------------------------------- Commit 8e5e03ad0dc6852ec9a1f3fab060b26e025f35f7 in deltaspike's branch refs/heads/master from Juri Berlanda [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=8e5e03a ] DELTASPIKE-1369: Remove unneeded throws from execute() methods. Signed-off-by: Juri Berlanda <juriberla...@hotmail.com> > [Scheduler] Enable/Disable based on custom condition > ---------------------------------------------------- > > Key: DELTASPIKE-1369 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1369 > Project: DeltaSpike > Issue Type: Improvement > Components: Scheduler > Reporter: Juri Berlanda > Priority: Major > > 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?- Found > * -Use 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)