anchor.diff:  `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 shared instance throughout Spring MVC.
   
   In more advanced cases, it may be useful to configure multiple
   `ContentNegotiationManager` instances that in turn may contain custom
  
positive.code: header may include wild cards, for example `text/{asterisk}`, in which case a `View` whose
  Content-Type was `text/xml` is a compatible match.
  
  To support the resolution of a view based on a file extension, use the
  `ContentNegotiatingViewResolver` bean property `mediaTypes` to specify a mapping of file
  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:`
  
  [source,xml,indent=0]
  [subs="verbatim,quotes"]
  ----
  	<bean class="org.springframework.web.servlet.view.ContentNegotiatingViewResolver">
  		<property name="mediaTypes">
  			<map>
  				<entry key="atom" value="application/atom+xml"/>
  				<entry key="html" value="text/html"/>
  				<entry key="json" value="application/json"/>
  			</map>
  		</property>
  		<property name="viewResolvers">
  			<list>
  				<bean class="org.springframework.web.servlet.view.BeanNameViewResolver"/>
  
negative.code: 		</property>
  		<property name="defaultViews">
  			<list>
  				<bean class="org.springframework.web.servlet.view.json.MappingJackson2JsonView"/>
  			</list>
  		</property>
  	</bean>
  