anchor.diff:  
   The preceding XML is more succinct. However, typos are discovered at runtime rather than
   design time, unless you use an IDE (such as https://www.jetbrains.com/idea/[IntelliJ
  -IDEA] or the https://spring.io/tools/sts[Spring Tool Suite])
  +IDEA] or the https://spring.io/tools[Spring Tool Suite])
   that supports automatic property completion when you create bean definitions. Such IDE
   assistance is highly recommended.
   
  
positive.code: still somewhat ambiguous. For example, as a developer looking at `ServiceConfig`, how do
  you know exactly where the `@Autowired AccountRepository` bean is declared? It is not
  explicit in the code, and this may be just fine. Remember that the
  https://spring.io/tools/sts[Spring Tool Suite] provides tooling that
  can render graphs showing how everything is wired, which may be all you need. Also,
  your Java IDE can easily find all declarations and uses of the `AccountRepository` type
  and quickly show you the location of `@Bean` methods that return that type.
  
negative.code: It is worth pointing out that through its <<beans-java, JavaConfig>> option, Spring lets
  annotations be used in a non-invasive way, without touching the target components
  source code and that, in terms of tooling, all configuration styles are supported by the
  https://spring.io/tools[Spring Tool Suite].
  ****
  
  An alternative to XML setup is provided by annotation-based configuration, which relies on
  