@RequestMapping: convention-based URL mapping at controller class level [SPR-5058]

[spring-projects-issues]

Yang Lifan opened SPR-5058 and commented

I think Spring MVC URL mapping is a disadvantage for Spring Web. ControllerClassNameHandlerMapping and BeanNameHandlerMapping are a little agile, but they can only map the url to the class level, can not support the method level.

In Spring MVC 2.5, DefaultAnnotationHandlerMapping is a new way for URL Mapping. Developers can use @RequestMapping to map a url to a class level or a method level. But the url is hard coded. And the url mapping value even has the url request suffix.

http://jira.springframework.org/browse/SPR-4125 The opinion in this report is valuable. Maybe there is a better solution. Whatever, currently, the url mapping strategy in Spring MVC need to be improved.

---

Affects: 2.5.5

Issue Links:

• Add convention-over-configuration support for @RequestMapping [SPR-4125] #8804 Add convention-over-configuration support for @RequestMapping
• Comprehensive REST Support [SPR-4419] #9097 Comprehensive REST Support

[spring-projects-issues]

Juergen Hoeller commented

As per my comment in #8804, conventional mappings at the method level are already supported, even without hardcoded URL suffix. The only actual gap, as far as I can see, is conventional URL mapping at the type level - while still using @RequestMapping, not an explicit ControllerClassNameHandlerMapping. We'll review this for Spring 3.0.

Juergen