Skip to content

Use MergedAnnotations API directly in AnnotationBeanNameGenerator where possible #31203

@sbrannen

Description

@sbrannen

AnnotationBeanNameGenerator was written before the introduction of the MergedAnnotations API and therefore heavily relies on the AnnotationMetadata abstraction and various helper methods for ASM compatibility.

However, recent work on determineBeanNameFromAnnotation(AnnotatedBeanDefinition) has made it apparent that we should use the MergedAnnotations API directly in AnnotationBeanNameGenerator where possible in order to avoid unnecessary, repeated iterations/streams over the same annotation metadata.

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: enhancementA general enhancement

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions