public class AsyncExecutionInterceptor extends AsyncExecutionAspectSupport implements MethodInterceptor, Ordered
MethodInterceptorthat processes method invocations asynchronously, using a given
AsyncTaskExecutor. Typically used with the
In terms of target method signatures, any parameter types are supported.
However, the return type is constrained to either
java.util.concurrent.Future. In the latter case, the Future handle
returned from the proxy will be an actual asynchronous Future that can be used
to track the result of the asynchronous method execution. However, since the
target method needs to implement the same signature, it will have to return
a temporary Future handle that just passes the return value through
or EJB 3.1's
As of Spring 3.1.2 the
AnnotationAsyncExecutionInterceptor subclass is
preferred for use due to its support for executor qualification in conjunction with
|Constructor and Description|
Create a new
|Modifier and Type||Method and Description|
Return the qualifier or bean name of the executor to be used when executing the given async method, typically specified in the form of an annotation attribute.
Return the order value of this object, with a higher value meaning greater in terms of sorting.
Intercept the given method invocation, submit the actual calling of the method to the correct task executor and return immediately to the caller.
determineAsyncExecutor, setBeanFactory, setExecutor
public Object invoke(MethodInvocation invocation) throws Throwable
nullindicates that no specific executor has been specified and that the default executor should be used.
This implementation is a no-op for compatibility in Spring 3.1.2. Subclasses may override to provide support for extracting qualifier information, e.g. via an annotation on the given method.
method- the method to inspect for executor qualifier metadata
public int getOrder()
Normally starting with 0, with
indicating the greatest value. Same order values will result
in arbitrary positions for the affected objects.
Higher values can be interpreted as lower priority. As a consequence, the object with the lowest value has highest priority (somewhat analogous to Servlet "load-on-startup" values).