From 49b8d8c482a9a63ced9ab98381421c4dc8a0345a Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Tue, 28 Mar 2017 10:05:33 +0200 Subject: [PATCH] Polish See gh-8698 --- spring-boot-docs/src/main/asciidoc/howto.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-docs/src/main/asciidoc/howto.adoc index 30eea92534..4de4be677e 100644 --- a/spring-boot-docs/src/main/asciidoc/howto.adoc +++ b/spring-boot-docs/src/main/asciidoc/howto.adoc @@ -1291,7 +1291,7 @@ modules when you add new features to your application. If you want to replace the default `ObjectMapper` completely, either define a `@Bean` of that type and mark it as `@Primary`, or, if you prefer the builder-based approach, define a `Jackson2ObjectMapperBuilder` `@Bean`. Note that in either case this -will disable all auto-configuration of the `ObjectMapper. +will disable all auto-configuration of the `ObjectMapper`. If you provide any `@Beans` of type `MappingJackson2HttpMessageConverter` then they will replace the default value in the MVC configuration. Also, a convenience bean is @@ -1777,7 +1777,7 @@ translation for you, you can configure it like this: NOTE: Because your custom configuration chooses to go with Hikari, `app.datasource.type` will have no effect. In practice the builder will be initialized with whatever value you -might set there and then overridden by the call to `.type()``. +might set there and then overridden by the call to `.type()`. See _<>_ in the '`Spring Boot features`' section and the