Class AccessorNamingStrategy.Base
- All Implemented Interfaces:
Serializable
- Enclosing class:
- AccessorNamingStrategy
- No getter or is-getter methods are recognized: relevant methods return
null
- No setter methods are recognized: relevant methods return
null
- Names of fields are returned as-is, without modifications (meaning they may be discovered if they are otherwise visible
- See Also:
-
Nested Class Summary
Nested classes/interfaces inherited from class edu.internet2.middleware.grouperClientExt.com.fasterxml.jackson.databind.introspect.AccessorNamingStrategy
AccessorNamingStrategy.Base, AccessorNamingStrategy.Provider
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionfindNameForIsGetter
(AnnotatedMethod method, String name) Method called to find whether given method would be considered an "is-getter" getter method in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)findNameForMutator
(AnnotatedMethod method, String name) Method called to find whether given method would be considered a "mutator" (usually setter, but for builders "with-method" or similar) in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)findNameForRegularGetter
(AnnotatedMethod method, String name) Method called to find whether given method would be considered a "regular" getter method in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)modifyFieldName
(AnnotatedField field, String name) Method called to find the name of logical property that given field should be associated with, if any.
-
Constructor Details
-
Base
public Base()
-
-
Method Details
-
findNameForIsGetter
Description copied from class:AccessorNamingStrategy
Method called to find whether given method would be considered an "is-getter" getter method in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)Note that signature acceptability has already been checked (no arguments, has return value) but NOT the specific limitation that return type should be of boolean type -- implementation should apply latter check, if so desired (some languages may use different criteria). It is also possible that some implementations allow different return types than boolean types.
Note that visibility checks are applied separately; strategy does not need to be concerned with that aspect.
- Specified by:
findNameForIsGetter
in classAccessorNamingStrategy
- Parameters:
method
- Method to checkname
- Name to check (usually same asAnnotatedMethod.getName()
- Returns:
- Implied property name for is-getter method, if match;
null
to indicate that the name does not conform to expected naming convention
-
findNameForRegularGetter
Description copied from class:AccessorNamingStrategy
Method called to find whether given method would be considered a "regular" getter method in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)Note that signature acceptability has already been checked (no arguments, does have a return value) by caller.
Note that this method MAY be called for potential "is-getter" methods too (before
AccessorNamingStrategy.findNameForIsGetter(edu.internet2.middleware.grouperClientExt.com.fasterxml.jackson.databind.introspect.AnnotatedMethod, java.lang.String)
)Note that visibility checks are applied separately; strategy does not need to be concerned with that aspect.
- Specified by:
findNameForRegularGetter
in classAccessorNamingStrategy
- Parameters:
method
- Method to checkname
- Name to check (usually same asAnnotatedMethod.getName()
- Returns:
- Implied property name for getter method, if match;
null
to indicate that the name does not conform to expected naming convention
-
findNameForMutator
Description copied from class:AccessorNamingStrategy
Method called to find whether given method would be considered a "mutator" (usually setter, but for builders "with-method" or similar) in context of type introspected, and if so, what is the logical property it is associated with (which in turn suggest external name for property)Note that signature acceptability has already been checked (exactly one parameter) by caller.
Note that visibility checks are applied separately; strategy does not need to be concerned with that aspect.
- Specified by:
findNameForMutator
in classAccessorNamingStrategy
- Parameters:
method
- Method to checkname
- Name to check (usually same asAnnotatedMethod.getName()
- Returns:
- Implied property name for mutator method, if match;
null
to indicate that the name does not conform to expected naming convention
-
modifyFieldName
Description copied from class:AccessorNamingStrategy
Method called to find the name of logical property that given field should be associated with, if any.Note that visibility checks are applied separately; strategy does not need to be concerned with that aspect.
- Specified by:
modifyFieldName
in classAccessorNamingStrategy
- Parameters:
field
- Field to checkname
- Name to check (usually same asAnnotatedField.getName()
- Returns:
- Implied property name matching given field (often field name as-is) or
null
to indicate that the name does not conform to expected naming convention (and will not be considered for property access)
-