See: Description
Interface | Description |
---|---|
MethodNameResolver | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
Class | Description |
---|---|
AbstractUrlMethodNameResolver | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
InternalPathMethodNameResolver | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
MultiActionController | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
ParameterMethodNameResolver | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
PropertiesMethodNameResolver | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
Exception | Description |
---|---|
NoSuchRequestHandlingMethodException | Deprecated
as of 4.3, in favor of annotation-driven handler methods
|
Typically a controller that handles multiple request types will extend MultiActionController, and implement multiple request handling methods that will be invoked by reflection if they follow this class' naming convention. Classes are analyzed at startup and methods cached, so the performance overhead of reflection in this approach is negligible.