@Target(value=TYPE) @Retention(value=RUNTIME) @Documented @FrameworkController @ResponseBody public @interface FrameworkRestController
This means that if FrameworkControllerScan is included in the application configuration
(and FrameworkRestController is in its FrameworkControllerScan.includeFilters()),
then the classes annotated with this will be component scanned and included in the application
context. The FrameworkMappings in these classes will be added to handler mappings with a
lower priority than RequestMappings found within
a class annotated with RestController. This
priority is achieved through FrameworkMappingHandlerMapping having a higher order
value than RequestMappingHandlerMapping.
The intention is that you are able to specify RESTful controllers and mappings within a framework module as the default REST endpoints and a client application can essentially override those mappings without causing an ambiguous mapping exception.
The site handler mappings in play in order of precedence from highest to lowest are:
RequestMappingHandlerMappingFrameworkMappingHandlerMappingFrameworkMapping,
FrameworkControllerScanCopyright © 2019. All rights reserved.