Reinstate support for legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations
#31090
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Comments
sbrannen
added
in: core
sbrannen
added a commit
to sbrannen/spring-framework
that referenced
this issue
Aug 22, 2023
…amed This commit reinstates support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations with regard to component name lookups. Support for component scanning will be added in a subsequent commit. See spring-projectsgh-31090
|
Current work on this feature can be viewed in the following feature branch: main...sbrannen:spring-framework:issues/gh-31090-legacy-ManagedBean-and-Named-annotations |
sbrannen
added a commit
to sbrannen/spring-framework
that referenced
this issue
Aug 23, 2023
…amed This commit reinstates support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations with regard to component name lookups. Support for component scanning will be added in a subsequent commit. See spring-projectsgh-31090
sbrannen
added a commit
to sbrannen/spring-framework
that referenced
this issue
Aug 23, 2023
…amed This commit reinstates support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations with regard to component scanning. See spring-projectsgh-31090
sbrannen
added a commit
to sbrannen/spring-framework
that referenced
this issue
Aug 26, 2023
…amed This commit reinstates support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations with regard to component name lookups and component scanning. Closes spring-projectsgh-31090
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the migration to Jakarta annotations in 6.0, we switched to supporting
@jakarta.annotation.ManagedBeanand@jakarta.inject.Namedannotations for component scanning and component name lookups.To better assist projects in the migration to Spring 6+, we should reinstate support for the legacy JSR-250
@javax.annotation.ManagedBeanand JSR-330@javax.inject.Namedannotations so that existing compiled code will continue to work as expected.Related Issues
javax.annotation.PostConstruct/PreDestroyand JSR-330javax.inject.Injectin addition to Jakarta EE 9 annotations #27444@javax.annotation.Resourceannotation #30695Deliverables
@javax.annotation.ManagedBeanand@javax.inject.NamedinClassPathScanningCandidateComponentProvider#registerDefaultFilters(...).@javax.annotation.ManagedBeanand@javax.inject.NamedinAnnotationBeanNameGenerator#isStereotypeWithNameValue(...).The text was updated successfully, but these errors were encountered: