Sam Brannen a199654a62 Use MergedAnnotations API in AnnotationBeanNameGenerator where feasible ...

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() has made it
apparent that we should use the MergedAnnotations API directly in
AnnotationBeanNameGenerator where feasible in order to avoid
unnecessary, repeated iterations/streams over the same annotation
metadata.

Closes gh-31203

2023-09-11 17:20:01 +02:00

..

jmh/java/org/springframework/context

Early removal of 5.x-deprecated code

2021-11-18 09:18:06 +01:00

main

Use MergedAnnotations API in AnnotationBeanNameGenerator where feasible

2023-09-11 17:20:01 +02:00

test

Reactive support in MethodValidationInterceptor

2023-09-06 12:54:06 +01:00

testFixtures/java/org/springframework/context/testfixture

Polish "Evaluate key only if necessary"

2023-07-14 14:43:04 +02:00