From acd34df0d5d28348cfafa0af60ed82b12eb3d9eb Mon Sep 17 00:00:00 2001 From: Marten Deinum Date: Fri, 1 Sep 2023 09:20:49 +0200 Subject: [PATCH] Fix WebFlux blocking configuration documentation BlockingExecutionConfigurer#setExecutor takes an AsyncTaskExecutor not an Executor as the documentation states. With this commit, this has been corrected. Closes gh-31150 --- framework-docs/modules/ROOT/pages/web/webflux/config.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/framework-docs/modules/ROOT/pages/web/webflux/config.adoc b/framework-docs/modules/ROOT/pages/web/webflux/config.adoc index a74d18f2ca..69e2f81957 100644 --- a/framework-docs/modules/ROOT/pages/web/webflux/config.adoc +++ b/framework-docs/modules/ROOT/pages/web/webflux/config.adoc @@ -745,7 +745,7 @@ reliance on it. The WebFlux Java config allows you to customize blocking execution in WebFlux. You can have blocking controller methods called on a separate thread by providing -an `Executor` such as the +an `AsyncTaskExecutor` such as the {api-spring-framework}/core/task/VirtualThreadTaskExecutor.html[`VirtualThreadTaskExecutor`] as follows: @@ -761,7 +761,7 @@ Java:: @Override public void configureBlockingExecution(BlockingExecutionConfigurer configurer) { - Executor executor = ... + AsyncTaskExecutor executor = ... configurer.setExecutor(executor); } }