[Spring Cloud Gateway MVC] route vs controller precedence

[lmbai]

Describe the bug
when use the Spring Cloud Gateway MVC with a self defined web controller, the route take more priority than controller. This is different behaviour with the Reactive Gateway

Sample
we have a controller

@GetMapping("/items/{Id}")

we also have a route definition

    gateway:
      mvc:
        routes:
          - id: Fallback
            uri: ${downtream-uri}
            predicates:
              - Path=/items/**

the request didn't reach to the controller, it directly route to downsteam