anchor.diff:  classpath). In addition Spring Boot will load a file `schema-${platform}.sql` where
   `platform` is the vendor name of the database (`hsqldb`, `h2`, `oracle`, `mysql`,
   `postgresql` etc.). Spring Boot enables the failfast feature of the Spring JDBC
  -initializer by default, so if the scripts cause exceptions the application will fail.
  +initializer by default, so if the scripts cause exceptions the application will fail
  +to start.
   
   To disable the failfast you can set `spring.datasource.continueOnError=true`. This can be
   useful once an application has matured and been deployed a few times, since the scripts
  
positive.code: 
  * `spring.config.name` (`SPRING_CONFIG_NAME`), defaults to `application` as the root of
    the file name.
  * `spring.config.location` (`SPRING_CONFIG_LOCATION`) is file to load (e.g. a classpath
    resource or a URL). A separate `Environment` property source is set up for this document
    and it can be overridden by system properties, environment variables or the
    command line.
  
negative.code: detects this automatically in the root of the classpath).
  
  Vanilla usage of Spring `DispatcherServlet` and Spring Security should require no further
  changes. If you have other features in your application, using other servlets or filters
  for instance, then you may need to add some configuration to your `Application` context,
  replacing those elements from the `web.xml` as follows:
  
  * A `@Bean` of type `Servlet` or `ServletRegistrationBean` installs that bean in the
  