From 87d0113b258f86755e82a04768db43a1a15fe3eb Mon Sep 17 00:00:00 2001 From: Tran Ngoc Nhan Date: Fri, 5 Dec 2025 20:10:16 +0700 Subject: [PATCH] Correct Reactive Libraries reference link Signed-off-by: Tran Ngoc Nhan --- framework-docs/modules/ROOT/pages/web/webflux-functional.adoc | 2 +- .../pages/web/webflux/controller/ann-methods/arguments.adoc | 2 +- .../web/webflux/controller/ann-methods/responseentity.adoc | 2 +- .../modules/ROOT/pages/web/webflux/new-framework.adoc | 4 ++-- .../modules/ROOT/pages/web/webmvc/mvc-ann-async.adoc | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/framework-docs/modules/ROOT/pages/web/webflux-functional.adoc b/framework-docs/modules/ROOT/pages/web/webflux-functional.adoc index a86167882c6..30e4a536570 100644 --- a/framework-docs/modules/ROOT/pages/web/webflux-functional.adoc +++ b/framework-docs/modules/ROOT/pages/web/webflux-functional.adoc @@ -123,7 +123,7 @@ Both request and response provide {reactive-streams-site}[Reactive Streams] back against the body streams. The request body is represented with a Reactor `Flux` or `Mono`. The response body is represented with any Reactive Streams `Publisher`, including `Flux` and `Mono`. -For more on that, see xref:web-reactive.adoc#webflux-reactive-libraries[Reactive Libraries]. +For more on that, see xref:web/webflux-reactive-libraries.adoc[Reactive Libraries]. [[webflux-fn-request]] === ServerRequest diff --git a/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/arguments.adoc b/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/arguments.adoc index d3b09d8e66f..160ba2926c7 100644 --- a/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/arguments.adoc +++ b/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/arguments.adoc @@ -5,7 +5,7 @@ The following table shows the supported controller method arguments. -Reactive types (Reactor, RxJava, xref:web-reactive.adoc#webflux-reactive-libraries[or other]) are +Reactive types (Reactor, RxJava, xref:web/webflux-reactive-libraries.adoc[or other]) are supported on arguments that require blocking I/O (for example, reading the request body) to be resolved. This is marked in the Description column. Reactive types are not expected on arguments that do not require blocking. diff --git a/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/responseentity.adoc b/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/responseentity.adoc index 6831075da2a..f7159a0754c 100644 --- a/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/responseentity.adoc +++ b/framework-docs/modules/ROOT/pages/web/webflux/controller/ann-methods/responseentity.adoc @@ -33,7 +33,7 @@ Kotlin:: ---- ====== -WebFlux supports using a single value xref:web-reactive.adoc#webflux-reactive-libraries[reactive type] to +WebFlux supports using a single value xref:web/webflux-reactive-libraries.adoc[reactive type] to produce the `ResponseEntity` asynchronously, and/or single and multi-value reactive types for the body. This allows a variety of async responses with `ResponseEntity` as follows: diff --git a/framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc b/framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc index f8f0062ceb1..a06734f22a6 100644 --- a/framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc +++ b/framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc @@ -77,7 +77,7 @@ as input, adapts it to a Reactor type internally, uses that, and returns either `Flux` or a `Mono` as output. So, you can pass any `Publisher` as input and you can apply operations on the output, but you need to adapt the output for use with another reactive library. Whenever feasible (for example, annotated controllers), WebFlux adapts transparently to the use -of RxJava or another reactive library. See xref:web-reactive.adoc#webflux-reactive-libraries[Reactive Libraries] for more details. +of RxJava or another reactive library. See xref:web/webflux-reactive-libraries.adoc[Reactive Libraries] for more details. NOTE: In addition to Reactive APIs, WebFlux can also be used with xref:languages/kotlin/coroutines.adoc[Coroutines] APIs in Kotlin which provides a more imperative style of programming. @@ -148,7 +148,7 @@ RxJava to perform blocking calls on a separate thread but you would not be makin most of a non-blocking web stack. * If you have a Spring MVC application with calls to remote services, try the reactive `WebClient`. -You can return reactive types (Reactor, RxJava, xref:web-reactive.adoc#webflux-reactive-libraries[or other]) +You can return reactive types (Reactor, RxJava, xref:web/webflux-reactive-libraries.adoc[or other]) directly from Spring MVC controller methods. The greater the latency per call or the interdependency among calls, the more dramatic the benefits. Spring MVC controllers can call other reactive components too. diff --git a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-async.adoc b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-async.adoc index b44f0828ade..17779b8aeb6 100644 --- a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-async.adoc +++ b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-async.adoc @@ -414,7 +414,7 @@ customize the status and headers of the response. [.small]#xref:web/webflux/reactive-spring.adoc#webflux-codecs-streaming[See equivalent in the Reactive stack]# Spring MVC supports use of reactive client libraries in a controller (also read -xref:web-reactive.adoc#webflux-reactive-libraries[Reactive Libraries] in the WebFlux section). +xref:web/webflux-reactive-libraries.adoc[Reactive Libraries] in the WebFlux section). This includes the `WebClient` from `spring-webflux` and others, such as Spring Data reactive data repositories. In such scenarios, it is convenient to be able to return reactive types from the controller method.