anchor.diff:  (The implicitly registered post-processors include
   {api-spring-framework}/beans/factory/annotation/AutowiredAnnotationBeanPostProcessor.html[`AutowiredAnnotationBeanPostProcessor`],
   {api-spring-framework}/context/annotation/CommonAnnotationBeanPostProcessor.html[`CommonAnnotationBeanPostProcessor`],
  -{api-spring-framework}/orm/jpa/support/PersistenceAnnotationBeanPostProcessor.html[`PersistenceAnnotationBeanPostProcessor`],
  -and the aforementioned
  +{api-spring-framework}/orm/jpa/support/PersistenceAnnotationBeanPostProcessor.html[`PersistenceAnnotationBeanPostProcessor`], and
   {api-spring-framework}/beans/factory/annotation/RequiredAnnotationBeanPostProcessor.html[`RequiredAnnotationBeanPostProcessor`].)
   
   [NOTE]
  
positive.code: ----
  
  
  [[beans-factory-extension-bpp-examples-rabpp]]
  ==== Example: The `RequiredAnnotationBeanPostProcessor`
  
  Using callback interfaces or annotations in conjunction with a custom
  `BeanPostProcessor` implementation is a common means of extending the Spring IoC
  container. An example is Spring's `RequiredAnnotationBeanPostProcessor` -- a
  `BeanPostProcessor` implementation that ships with the Spring distribution and that ensures
  that JavaBean properties on beans that are marked with an (arbitrary) annotation are
  actually (configured to be) dependency-injected with a value.
  
  [NOTE]
  ====
  The `@RequiredAnnotationBeanPostProcessor` is formally deprecated as of Spring Framework 5.1,
  see NOTE in <<beans-required-annotation,`@Required`>> annotation for details.
  ====
  
  [[beans-factory-extension-bpp-examples-aabpp]]
  ==== Example: The `AutowiredAnnotationBeanPostProcessor`
  
  Using callback interfaces or annotations in conjunction with a custom
  `BeanPostProcessor` implementation is a common means of extending the Spring IoC
  container. An example is Spring's `AutowiredAnnotationBeanPostProcessor` -- a
  `BeanPostProcessor` implementation that ships with the Spring distribution and autowires
  annotated fields, setter methods, and arbitrary config methods.
  
  
  
  
negative.code: }
  ----
  
  This annotation indicates that the affected bean property must be populated at
  configuration time, through an explicit property value in a bean definition or through
  autowiring. The container throws an exception if the affected bean property has not been
  