Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add comment why and how we handle Mono->CompletableFuture

Browse Source
This commit is contained in:
Artem Bilan
2024-07-03 12:42:10 -04:00
parent 1cea029fab
commit 4e7caed979
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
spring-integration-core/src/main/java/org/springframework/integration/handler/AbstractMessageProducingHandler.java
View File

@@ -384,7 +384,14 @@ public abstract class AbstractMessageProducingHandler extends AbstractMessageHan
reactiveReply
.publishOn(Schedulers.boundedElastic())
// TODO until Reactor supports context propagation from the MonoToCompletableFuture
/*
The MonoToCompletableFuture in Project Reactor does not support context propagation,
and it does not suppose to, since there is no guarantee how this Future is going to
be handled downstream.
However, in our case we process it directly in this class in the doProduceOutput()
via whenComplete() callback. So, when value is set into the Future, it is available
in the callback in the same thread immediately.
*/
.doOnEach((signal) -> {
try (AutoCloseable scope = IntegrationReactiveUtils
.setThreadLocalsFromReactorContext(signal.getContextView())) {