GH-9617: @SuppressWarnings("removal") for ListenableFuture
Fixes: #9617 Issue link: https://github.com/spring-projects/spring-integration/issues/9617 The `ListenableFuture` is marked `forRemoval` in Spring Framework. So, fix the code base to use `@SuppressWarnings("removal")`. Also, add a warning into logs that `ListenableFuture` support will be removed in `7.0`. * Fix JavaDocs where `ListenableFuture` is mentioned in favor of `CompletableFuture`
This commit is contained in:
@@ -618,9 +618,6 @@ There are two modes of operation when returning this type:
|
||||
* When the async executor is explicitly set to `null` and the return type is `CompletableFuture` or the return type is a subclass of `CompletableFuture`, the flow is invoked on the caller's thread.
|
||||
In this scenario, the downstream flow is expected to return a `CompletableFuture` of the appropriate type.
|
||||
|
||||
NOTE: The `org.springframework.util.concurrent.ListenableFuture` has been deprecated starting with Spring Framework `6.0`.
|
||||
It is recommended now to migrate to the `CompletableFuture` which provides similar processing functionality.
|
||||
|
||||
[[usage-scenarios]]
|
||||
==== Usage Scenarios
|
||||
|
||||
|
||||
Reference in New Issue
Block a user