Overview

As asked, this is a copy paste of #33345.

This regression is done again in version 7: 949432c.

Original Text

With the migration to Jakarta annotations in 7.0, we switched to supporting @jakarta.annotation.ManagedBean and @jakarta.inject.Named annotations for component scanning and component name lookups.

To better assist projects in the migration to Spring 6+ and 7+, we should reinstate support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations so that existing compiled code will continue to work as expected.

Deliverables

• Support @javax.annotation.ManagedBean and @javax.inject.Named in ClassPathScanningCandidateComponentProvider#registerDefaultFilters(...).
• Support @javax.annotation.ManagedBean and @javax.inject.Named in AnnotationBeanNameGenerator#isStereotypeWithNameValue(...).
• Update tests.
• Update Javadoc.

Related Issues

• Retain support for legacy JSR-250 javax.annotation.PostConstruct/PreDestroy and JSR-330 javax.inject.Inject in addition to Jakarta EE 9 annotations #27444
• Reinstate dependency injection support for legacy JSR-250 @javax.annotation.Resource annotation #30695
• Reinstate support for legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations #31090
• Reinstate qualifier support for legacy JSR-330 @javax.inject.Named annotation #33345