public interface SchedulingTaskExecutor extends AsyncTaskExecutor
TaskExecutorextension exposing scheduling characteristics that are relevant to potential task submitters.
Scheduling clients are encouraged to submit
Runnables that match the exposed preferences
TaskExecutor implementation in use.
SchedulingTaskExecutor implementations are encouraged to also
interface. This is not required due to the dependency on Spring 4.0's new
which would make it impossible for third-party executor implementations
to remain compatible with both Spring 4.0 and Spring 3.x.
|Modifier and Type||Method and Description|
execute, submit, submit
TaskExecutorprefer short-lived tasks over long-lived tasks?
SchedulingTaskExecutor implementation can indicate
whether it prefers submitted tasks to perform as little work as they
can within a single task execution. For example, submitted tasks
might break a repeated loop into individual subtasks which submit a
follow-up task afterwards (if feasible).
This should be considered a hint. Of course
clients are free to ignore this flag and hence the
SchedulingTaskExecutor interface overall. However, thread
pools will usually indicated a preference for short-lived tasks, to be
able to perform more fine-grained scheduling.
TaskExecutorprefers short-lived tasks