From 67d1f355d7f6ffa9ad2af45a900153b76ef60d40 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Wed, 6 Jan 2021 14:23:38 +0100 Subject: [PATCH] Fix Nullable reference See gh-24647 --- .../src/docs/asciidoc/production-ready-features.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc index 3416c88c0d30..a2fe54712744 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc @@ -467,7 +467,7 @@ Operations on an endpoint receive input via their parameters. When exposed via the web, the values for these parameters are taken from the URL's query parameters and from the JSON request body. When exposed via JMX, the parameters are mapped to the parameters of the MBean's operations. Parameters are required by default. -They can be made optional by annotating them with either `@javax.annotation.Nonnull` or `@org.springframework.lang.Nullable`. +They can be made optional by annotating them with either `@javax.annotation.Nullable` or `@org.springframework.lang.Nullable`. Each root property in the JSON request body can be mapped to a parameter of the endpoint. Consider the following JSON request body: