org.springframework.scheduling.backportconcurrent Documentation Differences

This file contains all the changes in documentation in the package org.springframework.scheduling.backportconcurrent as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Adapter that takes a JSR-166 backport edu.emory.mathcs.backport.java.util.concurrent.Executor and exposes a Spring org.springframework.core.task.TaskExecutor for it.

NOTE: This class implements Spring's org.springframework.core.task.TaskExecutor interface (and hence implicitly the standard Java 5 java.util.concurrent.Executor interface) as well as the JSR-166 edu.emory.mathcs.backport.java.util.concurrent.Executor interface, with the former being the primary interface, the other just serving as secondary convenience. For this reason, the exception handling follows the TaskExecutor contract rather than the backport Executor contract, in particular regarding the org.springframework.core.task.TaskRejectedException.

Note that there is a pre-built ThreadPoolTaskExecutor that allows for defining a JSR-166 backport edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor in bean style, exposing it as a Spring org.springframework.core.task.TaskExecutor directly. This is a convenient alternative to a raw ThreadPoolExecutor definition with a separate definition of the present adapter class. @author Juergen Hoeller @since 2.0.3 @see edu.emory.mathcs.backport.java.util.concurrent.Executor @see edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor @see edu.emory.mathcs.backport.java.util.concurrent.Executors @see ThreadPoolTaskExecutorThreadPoolTaskExecutor @deprecated as of Spring 3.2, in favor of using the native JDK 6 concurrent support

Implementation of the JSR-166 backport edu.emory.mathcs.backport.java.util.concurrent.ThreadFactory interface, allowing for customizing the created threads (name, priority, etc).

See the base class org.springframework.util.CustomizableThreadCreator for details on the available configuration options. @author Juergen Hoeller @since 2.0.3 @see #setThreadNamePrefix @see #setThreadPrioritysetThreadPriority @deprecated as of Spring 3.2, in favor of using the native JDK 6 concurrent support

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 org.springframework.core.task.TaskExecutor. This is an alternative to configuring a ThreadPoolExecutor instance directly using constructor injection, with a separate ConcurrentTaskExecutor adapter wrapping it.

For any custom needs, in particular for defining a edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor, it is recommended to use a straight definition of the Executor instance or a factory method definition that points to the JSR-166 backport edu.emory.mathcs.backport.java.util.concurrent.Executors class. To expose such a raw Executor as a Spring org.springframework.core.task.TaskExecutor, simply wrap it with a ConcurrentTaskExecutor adapter.

NOTE: This class implements Spring's org.springframework.core.task.TaskExecutor interface (and hence implicitly the standard Java 5 java.util.concurrent.Executor interface) as well as the JSR-166 edu.emory.mathcs.backport.java.util.concurrent.Executor interface, with the former being the primary interface, the other just serving as secondary convenience. For this reason, the exception handling follows the TaskExecutor contract rather than the backport Executor contract, in particular regarding the org.springframework.core.task.TaskRejectedException. @author Juergen Hoeller @since 2.0.3 @see org.springframework.core.task.TaskExecutor @see edu.emory.mathcs.backport.java.util.concurrent.Executor @see edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor @see edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor @see edu.emory.mathcs.backport.java.util.concurrent.Executors @see ConcurrentTaskExecutorConcurrentTaskExecutor @deprecated as of Spring 3.2, in favor of using the native JDK 6 concurrent support