This file contains all the changes in documentation in the package org.springframework.web.context.request.async 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.

Intercepts concurrent request handling, where the concurrent result is
obtained by executing a Callable on behalf of the application with
an AsyncTaskExecutor.

A [email protected] CallableProcessingInterceptor} is invoked before and after the
invocation of the [email protected] Callable} task in the asynchronous thread, as well
as on timeout from a container thread, or after completing for any reason
including a timeout or network error.

As a general rule exceptions raised by interceptor methods will cause
async processing to resume by dispatching back to the container and using
the Exception instance as the concurrent result. Such exceptions will then
be processed through the [email protected] HandlerExceptionResolver} mechanism.

The afterTimeout method
can select a value to be used to resume processing.
@author Rossen Stoyanchev
@since 3.2

Intercepts concurrent request handling, where the concurrent result is
obtained by waiting for a DeferredResult to be set from a thread
chosen by the application (e.g. in response to some external event).

A [email protected] DeferredResultProcessingInterceptor} is invoked before the start
of async processing, after the [email protected] DeferredResult} is set as well as on
timeout, or or after completing for any reason including a timeout or network
error.

As a general rule exceptions raised by interceptor methods will cause
async processing to resume by dispatching back to the container and using
the Exception instance as the concurrent result. Such exceptions will then
be processed through the [email protected] HandlerExceptionResolver} mechanism.