anchor.diff:  ----
   
   If you use JTA in a Java EE container, then you use a container `DataSource`, obtained
  -through JNDI, in conjunction with Spring's `JtaTransactionManager`. The following example shows what the JTA
  -and JNDI lookup version would look like:
  +through JNDI, in conjunction with Spring's `JtaTransactionManager`. The following example
  +shows what the JTA and JNDI lookup version would look like:
   
   [source,xml,indent=0,subs="verbatim,quotes"]
   ----
  
positive.code: 	}
  ---- 
  
  The reactive transaction manager is primarily a service provider interface (SPI), 
  although you can use it <<transaction-programmatic-rtm, programmatically>> from your 
  application code. Because `ReactiveTransactionManager` is an interface, it can 
  be easily mocked or stubbed as necessary. 
  
  The `TransactionDefinition` interface specifies:
  
  
negative.code: 	}
  ----
  
  In the preceding example, we used the syntax to define the transaction manager qualifier,
  but we could also have included propagation behavior, rollback rules, timeouts, and other
  features.
  
  
  [[tx-propagation]]
  