@ -32623,7 +32623,7 @@ To support the resolution of a view based on a file extension, use the
@@ -32623,7 +32623,7 @@ To support the resolution of a view based on a file extension, use the
extensions to media types. For more information on the algorithm used to determine the
request media type, refer to the API documentation for `ContentNegotiatingViewResolver`.
Here is an example configuration of a `ContentNegotiatingViewResolver:`
Here is an example configuration of a `ContentNegotiatingViewResolver`:
[source,xml,indent=0]
[subs="verbatim,quotes"]
@ -32647,7 +32647,7 @@ Here is an example configuration of a `ContentNegotiatingViewResolver:`
@@ -32647,7 +32647,7 @@ Here is an example configuration of a `ContentNegotiatingViewResolver:`
@ -34250,11 +34250,11 @@ that in turn can be created with a `ContentNegotiationManagerFactoryBean`:
@@ -34250,11 +34250,11 @@ that in turn can be created with a `ContentNegotiationManagerFactoryBean`:
@ -34270,7 +34270,7 @@ for request mapping purposes, and `RequestMappingHandlerAdapter` and
@@ -34270,7 +34270,7 @@ for request mapping purposes, and `RequestMappingHandlerAdapter` and
`ExceptionHandlerExceptionResolver` for content negotiation purposes.
Note that `ContentNegotiatingViewResolver` now can also be configured with a
`ContentNegotiatingViewResolver`, so you can use one instance throughout Spring MVC.
`ContentNegotiationManager`, so you can use one instance throughout Spring MVC.
In more advanced cases, it may be useful to configure multiple
`ContentNegotiationManager` instances that in turn may contain custom
@ -34346,10 +34346,10 @@ And the same in XML:
@@ -34346,10 +34346,10 @@ And the same in XML:
@ -34365,14 +34365,14 @@ The MVC namespace provides dedicated elements. For example with FreeMarker:
@@ -34365,14 +34365,14 @@ The MVC namespace provides dedicated elements. For example with FreeMarker:
@ -34689,11 +34689,11 @@ And the same in XML, use the `<mvc:path-matching>` element:
@@ -34689,11 +34689,11 @@ And the same in XML, use the `<mvc:path-matching>` element: