org.springframework.scheduling.SchedulingTaskExecutor |
Known Indirect Subclasses
ConcurrentTaskExecutor |
Adapter that takes a JSR-166 backport
edu.emory.mathcs.backport.java.util.concurrent.Executor and
exposes a Spring TaskExecutor for it. |
ConcurrentTaskScheduler |
Adapter that takes a JDK 1.5 java.util.concurrent.ScheduledExecutorService
and exposes a Spring TaskScheduler for it. |
GlassFishWorkManagerTaskExecutor |
Spring TaskExecutor adapter for the GlassFish JCA WorkManager. |
JBossWorkManagerTaskExecutor |
Spring TaskExecutor adapter for the JBoss JCA WorkManager. |
SimpleThreadPoolTaskExecutor |
Subclass of Quartz's SimpleThreadPool that implements Spring's
TaskExecutor interface
and listens to Spring lifecycle callbacks. |
ThreadPoolTaskExecutor |
JavaBean that allows for configuring a JSR-166 backport
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor in bean
style (through its "corePoolSize", "maxPoolSize", "keepAliveSeconds", "queueCapacity"
properties), exposing it as a Spring TaskExecutor . |
ThreadPoolTaskScheduler |
Implementation of Spring's TaskScheduler interface, wrapping
a native java.util.concurrent.ScheduledThreadPoolExecutor. |
TimerTaskExecutor |
This class is deprecated.
as of Spring 3.0, in favor of the scheduling.concurrent
package which is based on Java 5's java.util.concurrent.ExecutorService
|
WorkManagerTaskExecutor |
TaskExecutor implementation that delegates to a CommonJ WorkManager,
implementing the commonj.work.WorkManager interface,
which either needs to be specified as reference or through the JNDI name. |
|
Class Overview
A TaskExecutor
extension exposing
scheduling characteristics that are relevant to potential task submitters.
Scheduling clients are encouraged to submit
Runnables
that match the exposed preferences
of the TaskExecutor
implementation in use.
Summary
Public Methods |
abstract
boolean
|
prefersShortLivedTasks()
Does this TaskExecutor prefer short-lived tasks over
long-lived tasks?
A SchedulingTaskExecutor implementation can indicate
whether it prefers submitted tasks to perform as little work as they
can within a single task execution.
|
Public Methods
public
abstract
boolean
prefersShortLivedTasks
()
Does this TaskExecutor
prefer short-lived tasks over
long-lived tasks?
A 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 TaskExecutor
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.
Returns
true
if this TaskExecutor
prefers
short-lived tasks