anchor.diff:  Servlet 3.0 support on deployment. Add an extension of that to your project and build a
   war file as normal. For more detail, see the
   http://spring.io/guides/gs/convert-jar-to-war[``Converting a jar Project to a war''] guide
  -on the spring.io website.
  +on the spring.io website and the sample below.
   
   The war file can also be executable if you use the Spring Boot build tools. In that case
   the embedded container classes (to launch Tomcat for instance) have to be added to the
  
positive.code: === Use Jetty instead of Tomcat
  The Spring Boot starters (`spring-boot-starter-web` in particular) use Tomcat as an
  embedded container by default. You need to exclude those dependencies and include the
  Jetty ones instead. Spring Boot provides Tomcat and Jetty dependencies bundled together
  as separate startes to help make this process as easy as possible.
  
  Example in Maven:
  
  
negative.code: [[howto-customize-the-responsebody-rendering]]
  === Customize the @ResponseBody rendering
  Spring uses `HttpMessageConverters` to render `@ResponseBody` (or responses from
  `@RestController`). You can contribute additional converters by simply adding beans of
  that type in a Spring Boot context. If a bean you add is of a type that would have been
  included by default anyway (like `MappingJackson2HttpMessageConverter` for JSON
  conversions) then it will replace the default value. A convenience bean is provided of
  