On the link above, we fell to problem, that even if we instantiate our own subclass of RequestMappingHandlerMapping, and put it in right order, before the processing of default bean instance, we're not able to override it, nor configure it.
Which is causing problems for example to implement @RequestCondition.
In XML, there should be possibility to ref our own implementation of these beans:
Not forcing us to use BeansPostProcessor, as an ugly solution to reconfigure default given beans.
Thanks for the suggestion. The key challenge is how to make this possible without introducing two (conflicting) ways of configuring the same thing. For example consider some of the options on mvc:annotation-driven:
The conversionService reference and the message-converters are used to customize the created RequestMappingHandlerAdapter. If there was a way to also provide a reference to custom RequestMappingHandlerAdapter, it should be intuitive how it relates to the above configuration if both were present. I know we can say it's illegal to have both but that doesn't help with usability.