From 62e08a5ebe1107febf11fc260edf800d9d8f42b2 Mon Sep 17 00:00:00 2001 From: Rossen Stoyanchev Date: Mon, 8 Aug 2016 16:48:44 -0400 Subject: [PATCH] Minor update to Spring Web Reactive chapter Issue: SPR-14565 --- src/asciidoc/web-reactive.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/asciidoc/web-reactive.adoc b/src/asciidoc/web-reactive.adoc index 7a5b50efef..4348609c93 100644 --- a/src/asciidoc/web-reactive.adoc +++ b/src/asciidoc/web-reactive.adoc @@ -83,8 +83,8 @@ many of the same algorithms. The end result is a programming model identical to today's Spring MVC but with support for reactive types and executed in a reactive manner. -For example a controller method can declare the following as an -`@RequestBody` method argument: +For example a controller method can declare a `@RequestBody` method argument +in any one of the following ways: * `Account account` -- the account is deserialized without blocking before the controller is invoked. @@ -94,7 +94,8 @@ to declare logic to be executed after the account is deserialized. * `Flux accounts` -- input streaming scenario. * `Observable accounts` -- input streaming with RxJava. -The above also applies to return value handling: +Similarly a controller can also an `@ResponseBody` return value +in any one of the following ways: * `Mono` -- serialize without blocking the given Account when the `Mono` completes. * `Singe` -- same but using RxJava.