Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow @Async to specify which executor to use [SPR-7043] #11705

Closed
spring-projects-issues opened this issue Mar 28, 2010 · 1 comment
Closed
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Mar 28, 2010

Kenny MacLeod opened SPR-7043 and commented

I would like to see an attribute added to the @Async annotation, which allows the specification of the name of the executor bean to be used for invocations on that method. This would be an alternative to specifying the executor name in the <task:annotation-driven/> element.

The use case is that sometimes you want multiple executors in a context, and different @Async-annotated beans need to use different executors. Currently, there is no way to do this - all @Async-annotated beans in a given context must use whichever executor is configured in the <task:annotation-driven/> element.


Affects: 3.0.1

Issue Links:

2 votes, 2 watchers

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Apr 15, 2011

Chris Beams commented

As already noted, this issue duplicates #11153; resolving it as such.

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant