Stereotype annotations like `@Service` should add `@AliasFor` for `@Component` [SPR-16066]

[spring-projects-issues]

Yanming Zhou opened SPR-16066 and commented

@Service is a specialization of @Component, like @GetMapping is a specialization of @RequestMapping, @Service should add @AliasFor like @GetMapping

@Component
public @interface Service
{
  @AliasFor(annotation=Component.class)
  String value() default "";
}

We can get metadata from annotation via unified code

Component component = AnnotatedElementUtils.getMergedAnnotation(clazz, @Component.class);
String beanName = component.value();

---

Referenced from: commits 43b5e21, 625737f

[spring-projects-issues]

Sam Brannen commented

Juergen Hoeller, any reason not to apply the same change to annotations such as @Configuration, @RestController, @ControllerAdvice, @RestControllerAdvice, etc.?

[spring-projects-issues]

Juergen Hoeller commented

Good point :-) I've added similar declarations to @Configuration and @RestController (with the alias pointing to @Controller in the latter case). The controller advices don't have a value attribute with bean name semantics, so don't seem applicable here.

[spring-projects-issues]

Sam Brannen commented

I've added similar declarations to @Configuration and @RestController (with the alias pointing to @Controller in the latter case).

Cool. Thanks!

The controller advices don't have a value attribute with bean name semantics, so don't seem applicable here.

MMmmmmmm... indeed. I just listed off stereotypes without actually checking the source code. ;-)