anchor.diff:  ----
   
   For setting the timeout of the session you can use the configprop:spring.session.timeout[] property.
  -If that property is not set with a Servlet web appplication, the auto-configuration falls back to the value of configprop:server.servlet.session.timeout[].
  +If that property is not set with a Servlet web application, the auto-configuration falls back to the value of configprop:server.servlet.session.timeout[].
   
   
   You can take control over Spring Session's configuration using `@Enable*HttpSession` (Servlet) or `@Enable*WebSession` (Reactive).
  
positive.code: When using deferred or lazy bootstrapping, the auto-configured `EntityManagerFactoryBuilder` will use the context's `AsyncTaskExecutor`, if any, as the bootstrap executor.
  If more than one exists, the one named `applicationTaskExecutor` will be used.
  
  NOTE: When using deferred or lazy bootstraping, make sure to defer any access to the JPA infrastructure after the application context bootstrap phase.
  
  TIP: We have barely scratched the surface of Spring Data JPA.
  For complete details, see the {spring-data-jdbc-docs}[Spring Data JPA reference documentation].
  
negative.code: * HikariCP
  * Tomcat pooling `Datasource`
  * Commons DBCP2
  * Oracle UCP & `OracleDataSource`
  * Spring Framework's `SimpleDriverDataSource`
  * H2 `JdbcDataSource`
  * PostgreSQL `PGSimpleDataSource`
  