anchor.diff:    describes all the beans. Configuration metadata can be specified by XML, Java code, or
     annotations.
   * For each bean, its dependencies are expressed in the form of properties, constructor
  -  arguments, or arguments to the static-factory method( if you use that instead of
  -  a normal constructor). These dependencies are provided to the bean, when the bean is
  +  arguments, or arguments to the static-factory method (if you use that instead of a
  +  normal constructor). These dependencies are provided to the bean, when the bean is
     actually created.
   * Each property or constructor argument is an actual definition of the value to set, or
     a reference to another bean in the container.
  
positive.code: interfaces.
  
  Thus, in the following example, the `customerPreferenceDao` field first looks for a bean
  named customerPreferenceDao and then falls back to a primary type match for the type
  `CustomerPreferenceDao`:
  
  ====
  
negative.code: [[beans-factory-lifecycle]]
  === Lifecycle Callbacks
  
  To interact with the container's management of the bean lifecycle, you can implement
  the Spring `InitializingBean` and `DisposableBean` interfaces. The container calls
  `afterPropertiesSet()` for the former and `destroy()` for the latter to let the bean
  perform certain actions upon initialization and destruction of your beans.
  
  