-
Notifications
You must be signed in to change notification settings - Fork 636
Switch to CompletableFuture #1473
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
Labels
Milestone
Comments
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 27, 2022
Resolves spring-projects#1473 Given the stability of the project, it was simplest to copy the `AsyncRabbitTemplate` rather than adding a lot of conditional code. **2.4.x only; I will submit a separate PR for main**
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 27, 2022
Resolves spring-projects#1473 Given the stability of the project, it was simplest to copy the `AsyncRabbitTemplate` rather than adding a lot of conditional code. **2.4.x only; I will submit a separate PR for main**
artembilan
pushed a commit
that referenced
this issue
Jul 27, 2022
Resolves #1473 Given the stability of the project, it was simplest to copy the `AsyncRabbitTemplate` rather than adding a lot of conditional code. **2.4.x only; I will submit a separate PR for main**
garyrussell
added a commit
that referenced
this issue
Jul 27, 2022
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 28, 2022
- to aid migration from 2.4.x to 3.0.x so that the return types will not change
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 28, 2022
- to aid migration from 2.4.x to 3.0.x so that the return types will not change
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 28, 2022
- to aid migration from 2.4.x to 3.0.x so that the return types will not change
artembilan
pushed a commit
that referenced
this issue
Jul 28, 2022
- to aid migration from 2.4.x to 3.0.x so that the return types will not change * Increase test coverage. * Fix since. * Add author to new files.
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 28, 2022
Resolves spring-projects#1473 Given the stability of the project, it was simplest to copy the `AsyncRabbitTemplate` rather than adding a lot of conditional code. **2.4.x only; I will submit a separate PR for main** spring-projectsGH-1473: Fix Unused Import spring-projectsGH-1473: Move RabbitFutures to Top Level Classes - to aid migration from 2.4.x to 3.0.x so that the return types will not change * Increase test coverage. * Fix since. * Add author to new files. Remove async template; rename async template2.
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Jul 28, 2022
Resolves spring-projects#1473 Given the stability of the project, it was simplest to copy the `AsyncRabbitTemplate` rather than adding a lot of conditional code. **2.4.x only; I will submit a separate PR for main** spring-projectsGH-1473: Fix Unused Import spring-projectsGH-1473: Move RabbitFutures to Top Level Classes - to aid migration from 2.4.x to 3.0.x so that the return types will not change * Increase test coverage. * Fix since. * Add author to new files. Remove async template; rename async template2.
artembilan
pushed a commit
that referenced
this issue
Jul 28, 2022
Resolves #1473 * Deprecate `AsyncRabbitTemplate2`. * Copy implementation from `AsyncRabbitTemplate2` to `AsyncRabbitTemplate` * Fix other `ListenableFuture` usages.
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Sep 13, 2022
See spring-projects#1473 See spring-projects#1480 - caused problems with Boot auto configuration - since 3.0 is a major release, switching to CF there is not onerous - retain `CompletableFuture` as an async return type
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Sep 13, 2022
See spring-projects#1473 See spring-projects#1480 Migration interfaces to assist moving to `CompletableFuture` have been removed from 2.4.x due to Boot auto configuration issues. Therefore, these interfaces never existed in a released version of 2.4.x.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spring is planning on deprecating ListenableFuture in 6.0.
spring-projects/spring-framework#27780
Add methods that use
CompletableFuture
to the templates and deprecate those that returnListenableFuture
so we can remove them and have a clean API in 3.0.The text was updated successfully, but these errors were encountered: