Closed
Description
Juergen Hoeller opened SPR-13248 and commented
Along the lines of #17827, AsyncAnnotationBeanPostProcessor
could find a TaskExecutor
bean by type and/or name in the context, avoiding the need to implement AsyncConfigurer
for that purpose.
Issue Links:
- ScheduledAnnotationBeanPostProcessor should fall back to default TaskScheduler by name [SPR-13236] #17827 ScheduledAnnotationBeanPostProcessor should fall back to default TaskScheduler by name
- Regression: AsyncAnnotationBeanPostProcessor fails on startup when encountering ambiguous TaskExecutor beans [SPR-13720] #18293 Regression: AsyncAnnotationBeanPostProcessor fails on startup when encountering ambiguous TaskExecutor beans
- Regression: Early instantiation of a bean prevents proxying for @Async in 4.2.x but works in 4.1.x [SPR-14030] #18602 Regression: Early instantiation of a bean prevents proxying for
@Async
in 4.2.x but works in 4.1.x - Consistently accept "taskExecutor" bean of type Executor (as stated in @EnableAsync's javadoc) [SPR-15566] #20125 Consistently accept "taskExecutor" bean of type Executor (as stated in
@EnableAsync
's javadoc) - SchedulingConfigurer's ScheduledTaskRegistrar should reliably shut down before TaskScheduler [SPR-15067] #19633 SchedulingConfigurer's ScheduledTaskRegistrar should reliably shut down before TaskScheduler
Referenced from: commits c3e57dd