anchor.diff:  ----
   	@Target({ElementType.METHOD, ElementType.TYPE})
   	@Retention(RetentionPolicy.RUNTIME)
  -	@Transactional(value = "order", label = "causal-consistency")
  +	@Transactional(transactionManager = "order", label = "causal-consistency")
   	public @interface OrderTx {
   	}
   
   	@Target({ElementType.METHOD, ElementType.TYPE})
   	@Retention(RetentionPolicy.RUNTIME)
  -	@Transactional(value = "account", label = "retryable")
  +	@Transactional(transactionManager = "account", label = "retryable")
   	public @interface AccountTx {
   	}
   ----
  
positive.code: 
  Most Spring applications need only a single transaction manager, but there may be
  situations where you want multiple independent transaction managers in a single
  application. You can use the `value` attribute of the `@Transactional` annotation to
  optionally specify the identity of the `PlatformTransactionManager` to be used.
  This can either be the bean name or the qualifier value of the transaction manager bean.
  For example, using the qualifier notation, you can combine the following Java code with
  the following transaction manager bean declarations in the application context:
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  .Java
  
negative.code: ----
  	@Target(AnnotationTarget.FUNCTION, AnnotationTarget.TYPE)
  	@Retention(AnnotationRetention.RUNTIME)
  	@Transactional(transactionManager = "order", label = ["causal-consistency"])
  	annotation class OrderTx
  
  	@Target(AnnotationTarget.FUNCTION, AnnotationTarget.TYPE)
  	@Retention(AnnotationRetention.RUNTIME)
  	@Transactional(transactionManager = "account", label = ["retryable"])
  	annotation class AccountTx
  ----
  
  The preceding annotations let us write the example from the previous section as follows:
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  .Java
  