spring-projects / spring-projects/spring-modulith
Use dedicated task executor for `@ApplicationModuleListener`s
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
@ApplicationModuleListeners need dedicated control over the Executor running them, for example, to enable tracing context propagation in the observability module. To contain the impact of such a customization, it makes sense to use a dedicated Executor.
Implementation considerations
- Register a dedicated
ThreadPoolTaskExecutor/SimpleAsyncTaskExecutorwith a dedicated name and refer to that from the@Asyncannotation on@ApplicationModuleListener(@ConditionalOnThreading,@ConditionalOnMissingBean)
References
- GH-637
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing @ApplicationModuleListener and its @Async handling, then inspect how @ConditionalOnThreading and @ConditionalOnMissingBean are used for executor configuration. Done means listeners use a dedicated ThreadPoolTaskExecutor or SimpleAsyncTaskExecutor by name, while allowing the documented customization and preserving conditional behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100