anchor.diff:  
   [[boot-features-spring-mvc-static-content]]
   ==== Static Content
  -By default Spring Boot will serve static content from a folder called `/static` (or
  +By default Spring Boot will serve static content from a directory called `/static` (or
   `/public` or `/resources` or `/META-INF/resources`) in the classpath or from the root
   of the `ServletContext`.  It uses the `ResourceHttpRequestHandler` from Spring MVC so you
   can modify that behavior by adding your own `WebMvcConfigurerAdapter` and overriding the
  
positive.code: http://www.webjars.org/[Webjars content]. Any resources with a path in `+/webjars/**+` will
  be served from jar files if they are packaged in the Webjars format.
  
  TIP: Do not use the `src/main/webapp` folder if your application will be packaged as a
  jar. Although this folder is a common standard, it will *only* work with war packaging
  and it will be silently ignored by most build tools if you generate a jar.
  
  
  
negative.code: Atomikos is a popular open source transaction manager which can be embedded into your
  Spring Boot application. You can use the `spring-boot-starter-jta-atomikos` Starter POM to
  pull in the appropriate Atomikos libraries. Spring Boot will auto-configure Atomikos and
  ensure that appropriate `depends-on` settings are applied to your Spring beans for correct
  startup and shutdown ordering.
  
  By default Atomikos transaction logs will be written to a `transaction-logs` directory in
  your application home directory (the directory in which your application jar file
  resides). You can customize this directory by setting a `spring.jta.log-dir` property in
  your `application.properties` file. Properties starting `spring.jta.` can also be used to
  customize the Atomikos `UserTransactionServiceImp`. See the
  {dc-spring-boot}/jta/atomikos/AtomikosProperties.{dc-ext}[`AtomikosProperties` Javadoc]
  for complete details.
  
  NOTE: To ensure that multiple transaction managers can safely coordinate the same
  