anchor.diff:  instance as you would any other Spring Bean. By default the instance will attempt to
   connect to a local in-memory server (a `NodeClient` in Elasticsearch terms), but you can
   switch to a remote server (i.e. a `TransportClient`) by setting
  -`spring.data.elasticsearch.clusterNodes` to a comma-separated '`host:port`' list.
  +`spring.data.elasticsearch.cluster-nodes` to a comma-separated '`host:port`' list.
   
   [source,java,indent=0]
   ----
  
positive.code: 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`
  
  The {sc-spring-boot}/jta/BitronixXAConnectionFactoryWrapper.{sc-ext}[BitronixXAConnectionFactoryWrapper]
  and {sc-spring-boot}/jta/BitronixXADataSourceWrapper.{sc-ext}[BitronixXADataSourceWrapper]
  
negative.code: [[boot-features-class-conditions]]
  ==== Class conditions
  The `@ConditionalOnClass` and `@ConditionalOnMissingClass` annotations allows configuration
  to be included based on the presence or absence of specific classes. Due to the fact that
  annotation metadata is parsed using http://asm.ow2.org/[ASM] you can actually use the
  `value` attribute to refer to the real class, even though that class might not actually
  appear on the running application classpath. You can also use the `name` attribute if you
  