[
https://issues.apache.org/jira/browse/DELTASPIKE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juri Berlanda updated DELTASPIKE-1369:
--------------------------------------
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?- 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]
was:
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 alays been. Being a Bean, it can be
customized via CDI mechanisms (Specializes, Alternative, etc.).
The Bean should provide the following signature:
boolean isSchedulerEnabled();
boolean shouldJobBeStarted(Class<T>);
TBD:
* Better name for shouldJobBeStarted?
* Use JobName in shouldJobBeStarted?
Development takes place at
https://github.com/j-be/deltaspike/tree/scheduler-control
> [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]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
