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

@Async documentation should not suggest deprecated classes #33805

Closed
gbaso opened this issue Oct 28, 2024 · 0 comments
Closed

@Async documentation should not suggest deprecated classes #33805

gbaso opened this issue Oct 28, 2024 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: documentation A documentation task
Milestone

Comments

@gbaso
Copy link

gbaso commented Oct 28, 2024

@Async javadoc suggests that you can refine the return type of the Future you are returning to ListenableFuture, and provide an AsyncResult as a value holder.

However, both ListenableFuture and AsyncResult are deprecated since 6.0, in favor of CompletableFuture. @Async documentation should reflect this and stop suggesting ListenableFuture as result type.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 28, 2024
@jhoeller jhoeller added type: documentation A documentation task in: core Issues in core modules (aop, beans, core, context, expression) and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Oct 28, 2024
@jhoeller jhoeller self-assigned this Oct 28, 2024
@jhoeller jhoeller added this to the 6.1.15 milestone Oct 28, 2024
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) type: documentation A documentation task
Projects
None yet
Development

No branches or pull requests

3 participants