Skip to content

Update ref docs regarding deprecated @Required annotation #26578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions src/docs/asciidoc/core/core-beans.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4326,6 +4326,21 @@ container. An example is Spring's `RequiredAnnotationBeanPostProcessor` -- a
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.



[[beans-factory-extension-factory-postprocessors]]
Expand Down