anchor.diff:  [[mvc-view-jsp-resolver]]
   === View Resolvers
   
  -When developing with JSPs, you typically declare a `InternalResourceViewResolver` bean.
  +When developing with JSPs, you typically declare an `InternalResourceViewResolver` bean.
   
   `InternalResourceViewResolver` can be used for dispatching to any Servlet resource but in
   particular for JSPs. As a best practice, we strongly encourage placing your JSP files in
  
positive.code: separate multiple errors on a given field) and also accepts a second parameter -- this
  time, a class name or style attribute. Note that FreeMarker can specify default
  values for the attributes parameter. The following example shows how to use the `formInput`
  and `showWErrors` macros:
  
  [source,xml,indent=0,subs="verbatim,quotes"]
  ----
  
negative.code: = View Technologies
  [.small]#<<web-reactive.adoc#webflux-view, WebFlux>>#
  
  The use of view technologies in Spring MVC is pluggable. Whether you decide to use
  Thymeleaf, Groovy Markup Templates, JSPs, or other technologies is primarily a matter of
  a configuration change. This chapter covers view technologies integrated with Spring MVC.
  We assume you are already familiar with <<mvc-viewresolver>>.
  
  WARNING: The views of a Spring MVC application live within the internal trust boundaries
  of that application. Views have access to all the beans of your application context. As
  such, it is not recommended to use Spring MVC's template support in applications where
  the templates are editable by external sources, since this can have security implications.
  
  [[mvc-view-thymeleaf]]
  == Thymeleaf
  