@Async Supporting ListenableFuture [SPR-11909]

[spring-projects-issues]

Ronald R. DiFrango opened SPR-11909 and commented

It would be nice if via the @Async/@EnableAsync annotations or via start-up configuration that instead of AsyncExecutionInterceptor calling executor.submit(), it would executor.submitListenable() provided the TaskExecutor supports it.

---

Affects: 4.0.5

Issue Links:

• @Async Supporting ListenableFuture not applied with AspectJ [SPR-12092] #16708 @Async Supporting ListenableFuture not applied with AspectJ

Referenced from: commits 46dc07a

[spring-projects-issues]

Juergen Hoeller commented

AsyncExecutionInterceptor automatically uses submitListenable if an @Async method signature indicates ListenableFuture now. The determineAsyncExecutor method wraps the target Executor in a TaskExecutorAdapter anyway, so it uses an AsyncListenableTaskExecutor check now and wraps if the target executor doesn't implement it already. Furthermore, AsyncResult implements ListenableFuture now, for convenient use within such ListenableFuture-declaring @Async methods.

Juergen

[spring-projects-issues]

Ronald R. DiFrango commented

Just curious, how does a method signature on an @Async method indicate that it supports ListenableFuture? Also, will this apply if the @Async is at the class level?

[spring-projects-issues]

Juergen Hoeller commented

It's a return type check: If a method declares a return type of ListenableFuture now, submitListenable will be used to fulfil that requirement. It doesn't matter whether @Async is being declared at the method or type level there. This is why AsyncResult has to implement ListenableFuture as well: Formally, that's what your method has to wrap its result value in then.

Juergen