Merge branch '3.3.x'
This commit is contained in:
commit
2953e9892a
|
@ -350,7 +350,7 @@ See {code-spring-boot-autoconfigure-src}/orm/jpa/JpaBaseConfiguration.java[`JpaB
|
||||||
|
|
||||||
Spring Data JPA and Spring Data Mongo can both automatically create `Repository` implementations for you.
|
Spring Data JPA and Spring Data Mongo can both automatically create `Repository` implementations for you.
|
||||||
If they are both present on the classpath, you might have to do some extra configuration to tell Spring Boot which repositories to create.
|
If they are both present on the classpath, you might have to do some extra configuration to tell Spring Boot which repositories to create.
|
||||||
The most explicit way to do that is to use the standard Spring Data `+@EnableJpaRepositories+` and `+@EnableMongoRepositories+` annotations and provide the location of your `Repository` interfaces.
|
The most explicit way to do that is to use the standard Spring Data `@EnableJpaRepositories` and `@EnableMongoRepositories` annotations and provide the location of your `Repository` interfaces.
|
||||||
|
|
||||||
There are also flags (`+spring.data.*.repositories.enabled+` and `+spring.data.*.repositories.type+`) that you can use to switch the auto-configured repositories on and off in external configuration.
|
There are also flags (`+spring.data.*.repositories.enabled+` and `+spring.data.*.repositories.type+`) that you can use to switch the auto-configured repositories on and off in external configuration.
|
||||||
Doing so is useful, for instance, in case you want to switch off the Mongo repositories and still use the auto-configured `MongoTemplate`.
|
Doing so is useful, for instance, in case you want to switch off the Mongo repositories and still use the auto-configured `MongoTemplate`.
|
||||||
|
|
|
@ -196,7 +196,7 @@ Doing so leaves all MVC configuration in your hands.
|
||||||
== Customize ViewResolvers
|
== Customize ViewResolvers
|
||||||
|
|
||||||
A `ViewResolver` is a core component of Spring MVC, translating view names in `@Controller` to actual `View` implementations.
|
A `ViewResolver` is a core component of Spring MVC, translating view names in `@Controller` to actual `View` implementations.
|
||||||
Note that `ViewResolvers` are mainly used in UI applications, rather than REST-style services (a `View` is not used to render a `@ResponseBody`).
|
Note that view resolvers are mainly used in UI applications, rather than REST-style services (a `View` is not used to render a `@ResponseBody`).
|
||||||
There are many implementations of `ViewResolver` to choose from, and Spring on its own is not opinionated about which ones you should use.
|
There are many implementations of `ViewResolver` to choose from, and Spring on its own is not opinionated about which ones you should use.
|
||||||
Spring Boot, on the other hand, installs one or two for you, depending on what it finds on the classpath and in the application context.
|
Spring Boot, on the other hand, installs one or two for you, depending on what it finds on the classpath and in the application context.
|
||||||
The `DispatcherServlet` uses all the resolvers it finds in the application context, trying each one in turn until it gets a result.
|
The `DispatcherServlet` uses all the resolvers it finds in the application context, trying each one in turn until it gets a result.
|
||||||
|
|
|
@ -152,7 +152,7 @@ This provider supports the following parameters:
|
||||||
|===
|
|===
|
||||||
|
|
||||||
|
|
||||||
The following metadata snippet corresponds to the standard `server.servlet.jsp.class-name` property that defines the `JspServlet` class name to use:
|
The following metadata snippet corresponds to the standard `server.servlet.jsp.class-name` property that defines the class name to use must be an `HttpServlet`:
|
||||||
|
|
||||||
[source,json]
|
[source,json]
|
||||||
----
|
----
|
||||||
|
|
Loading…
Reference in New Issue