anchor.diff:  as regular `ConnectionFactory` and `DataSource` beans which will transparently enroll in
   the distributed transaction. DataSource and JMS auto-configuration will use JTA variants
   as long as you have a `JtaTransactionManager` bean and appropriate XA wrapper beans
  -registered within your `ApplicationContext`
  +registered within your `ApplicationContext`.
   
   The {sc-spring-boot}/jta/BitronixXAConnectionFactoryWrapper.{sc-ext}[BitronixXAConnectionFactoryWrapper]
   and {sc-spring-boot}/jta/BitronixXADataSourceWrapper.{sc-ext}[BitronixXADataSourceWrapper]
  
positive.code: [[boot-features-bean-conditions]]
  ==== Bean conditions
  The `@ConditionalOnBean` and `@ConditionalOnMissingBean` annotations allow configurations
  to be skipped based on the presence or absence of specific beans. You can use the `value`
  attribute to specify beans by type, or `name` to specify beans by name. The `search`
  attribute allows you to limit the `ApplicationContext` hierarchy that should be considered
  when searching for beans.
  
  NOTE: `@Conditional` annotations are processed when `@Configuration` classes are
  parsed. Auto-configure `@Configuration` is always parsed last (after any user defined
  beans), however, if you are using these annotations on regular `@Configuration` classes,
  care must be taken not to refer to bean definitions that have not yet been created.
  
  
negative.code: 
  [[boot-features-spring-mvc-static-content]]
  ==== Static Content
  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
  