@RestController should accept a bean name value [SPR-11360]

[spring-projects-issues]

Jens Alm opened SPR-11360 and commented

The @RestController does not take a value to be used as bean name. I currently have two controllers exporting different versions of the same service. The different controllers reside in different packages but are named the same thing. When the context starts up I get an exception for having two conflicting beans of the same name. When using the RestController annotation it defaults to the class name which in my case is the same so the conflict is legitimate. I would like to be able to specify a name for each one like you can with @Controller. As it is I had to rename a the classes to get it to work.

---

Affects: 4.0 GA

Referenced from: commits 7854277

[spring-projects-issues]

Sam Brannen commented

This has been resolved as described in the comments for GitHub commit 7854277:

Introduce value attribute in @RestController

Stereotype annotations should support a 'value' attribute for
specifying the name of the Spring-managed component; however,
@RestController currently does not provide such an attribute.

This commit introduces a 'value' attribute in @RestController so that
developers can provide custom names for components annotated with
@RestController.