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: 		</property>
  		<property name="defaultViews">
  			<list>
  				<bean class="org.springframework.web.servlet.view.json.MappingJackson2JsonView" />
  			</list>
  		</property>
  	</bean>
  
negative.code: 	<mvc:annotation-driven content-negotiation-manager="contentNegotiationManager" />
  
  	<bean id="contentNegotiationManager" class="org.springframework.web.accept.ContentNegotiationManagerFactoryBean">
  		<property name="favorPathExtension" value="false"/>
  		<property name="favorParameter" value="true"/>
  		<property name="mediaTypes">
  			<value>
  				json=application/json
  				xml=application/xml
  