Annotation Interface FrameworkMapping
This annotation behaves exactly like
RequestMapping except it is used inside FrameworkController and
FrameworkRestController controllers.
This reasoning for this annotation instead of just using RequestMapping is that when framework controllers
haven't been enabled and a framework controller is extended by a class annotated with Controller or RestController then the
undesired RequestMappings will get picked up once again due to Spring's annotation inheritance mechanics.
- Since:
- 5.2
- See Also:
-
RequestMappingFrameworkControllerFrameworkRestController
-
Optional Element Summary
Optional Elements
-
Element Details
-
name
String name- See Also:
-
RequestMapping.name()
- Default:
- ""
-
value
- See Also:
-
RequestMapping.value()
- Default:
- {}
-
path
- See Also:
-
RequestMapping.path()
- Default:
- {}
-
method
org.springframework.web.bind.annotation.RequestMethod[] method- See Also:
-
RequestMapping.method()
- Default:
- {}
-
params
String[] params- See Also:
-
RequestMapping.params()
- Default:
- {}
-
headers
String[] headers- See Also:
-
RequestMapping.headers()
- Default:
- {}
-
consumes
String[] consumes- See Also:
-
RequestMapping.consumes()
- Default:
- {}
-
produces
String[] produces- See Also:
-
RequestMapping.produces()
- Default:
- {}
-