ScheduledAnnotationBeanPostProcessor should fall back to default TaskScheduler by name [SPR-13236]

[spring-projects-issues]

Dave Syer opened SPR-13236 and commented

Spring Integration creates a bean of type TaskScheduler but only if it doesn't find one using a sensible search strategy. The strategy in ScheduledAnnotationBeanPostProcessor is different and not as sensible IMO (it has no fallback to a well-known bean name if there are multiple instances). This can be surprising for users.

See discussion here for background: spring-projects/spring-boot#3508, spring-attic/spring-xd#1747 (comment)

---

Affects: 4.2 RC2

Issue Links:

• 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)
• AsyncAnnotationBeanPostProcessor could find TaskExecutor by type/name [SPR-13248] #17839 AsyncAnnotationBeanPostProcessor could find TaskExecutor by type/name

[spring-projects-issues]

Juergen Hoeller commented

It's not too hard to fall back to a bean named "taskScheduler" in ScheduledAnnotationBeanPostProcessor, so we're doing that as of 4.2 GA now. Give it an early try please...

Note that marking the desired scheduler bean as primary is usually a fine solution to the problem, at least when the user has influence on the affected bean definitions.

Juergen

[spring-projects-issues]

Dave Syer commented

That seems to work nicely, thanks.