I'm voting for this issue for similar reasons I voted for
SPR-5087 - to recap, at my company we've currently got a lot of work coming up that will involve us creating a wide-variety of webapps that confirm to a certain set of rules around their restful urls. Annotated controllers are good for this kind of work but they actually give us somewhat more freedom than we need, and so we're introducing our own set of domain-specific annotations that let us create controller-like objects - not using @Controller, @Request, @RequestParam etc, but annotations that are expressive and leave less room for error within our own specific domain.
SPR-5087 I was considering creating my own HandlerAdapter to achieve this, but it might also be possible to re-use AnnotationMethodHandlerAdapter if the currently-private getMethodResolver() method could be overridden to create a HandlerMethodResolver of my own devising. For my particular use-case the HandlerMethodResolver would still need to expose the resolveHandlerMethod(HttpServletRequest) method that is added by ServletHandlerMethodResolver so that AnnotationMethodHandlerAdapter can call it, but the innards of the class would be more-or-less be completely replaced, so maybe 'ServletHandlerMethodResolver' would become an interface, and the current implementation would be pushed down into a 'RequestMappingAnnotatedHandlerMethodResolver'... or something with a shorter name.