Allow user to order rest handler mapping [DATAREST-896]

Petar Tahchiev opened DATAREST-896 and commented

As indicated here

https://github.com/spring-projects/spring-boot/blob/master/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/endpoint/mvc/EndpointHandlerMapping.java#L85

the RequestMappingHandlerMapping has order 0.

At the moment DelegatingHandlerMapping is registered with Ordered.LOWEST_PRECEDENCE - 100; so it is always after RequestMappingHandlerMapping. In a typical spring-boot application I would love to be able to configure the order. The best combination in my oppinion would be:

1) Some custom handler mapping or maybe h2-console?
2) Spring boot actuators
3) Spring data rest handler mapping 
4) RequestMappingHanderMapping (has order 0)
5) Static resources

but at the moment it is like this:

1) Some custom handler mapping or maybe h2-console?
2) Spring boot actuators
3) RequestMappingHanderMapping (has order 0)
4) Spring data rest handler mapping 
5) Static resources

In my application I have a DefaultController which always kicks in if there's no controller mapping, so I never get to the REST handler mapping.

Affects: 2.5.2 (Hopper SR2), 2.6 M1 (Ingalls)

3 votes, 6 watchers