Instances of this interface are used to configure tasks with input values (properties) that are resolved from the SDKReferences in the caller context.
Clients may implement this interface. When doing so, make sure to adhere to the hashCode() and
equals(
Use create(
| public static SDKPropertyReference | Creates a new SDKPropertyReference that resolves the property for a given identifier. |
| public static SDKPropertyReference | createWithFormat( Creates a new SDKPropertyReference that derives the property value using the given format and associated
arguments. |
| public boolean | Indicates whether some other object is "equal to" this one. |
| public String | getProperty( Call getValue( |
| public String | Call getValue( |
| public default String | getValue( Gets the derived value based on the arugment SDKs. |
| public int | hashCode() Returns a hash code value for the object. |
From: SDKValueReference< |
The created property references simply uses SDKReference.getProperty(
null.Each argument SDKValueReference will be evaluated in the caller SDK context and the results are formatted with the given format string.
null.
The equals method implements an equivalence relation on non-null object references:
- It is reflexive: for any non-null reference value
x,x.equals(x)should returntrue. - It is symmetric: for any non-null reference values
xandy,x.equals(y)should returntrueif and only ify.equals(x)returnstrue. - It is transitive: for any non-null reference values
x,y, andz, ifx.equals(y)returnstrueandy.equals(z)returnstrue, thenx.equals(z)should returntrue. - It is consistent: for any non-null reference values
xandy, multiple invocations ofx.equals(y)consistently returntrueor consistently returnfalse, provided no information used inequalscomparisons on the objects is modified. - For any non-null reference value
x,x.equals(null)should returnfalse.
The equals method for class Object implements the most discriminating possible equivalence
relation on objects; that is, for any non-null reference values x and y, this method returns
true if and only if x and y refer to the same object (x == y has the value
true).
Note that it is generally necessary to override the hashCode method whenever this method is overridden,
so as to maintain the general contract for the hashCode method, which states that equal objects must have
equal hash codes.
true if this object is the same as the obj argument; false otherwise.The implementation will retrieve the property in an implementation dependent manner.
The argument SDK is the one that is associated with the SDK name in the context of the operation.
If the property cannot be retrieved from the SDK, then the method may return null or throw an
exception.
null if the resolution failed.The method can access the information accessible via the argument SDKs and construct the return value based on that.
The result can be null, but implementations are encouraged to throw an appropriate exception
instead.
null.null.
The general contract of hashCode is:
- Whenever it is invoked on the same object more than once during an execution of a Java application, the
hashCodemethod must consistently return the same integer, provided no information used inequalscomparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application. - If two objects are equal according to the
equals(Object)method, then calling thehashCodemethod on each of the two objects must produce the same integer result. - It is not required that if two objects are unequal according to the
Object.equals(
Object) method, then calling thehashCodemethod on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hash tables.
As much as is reasonably practical, the hashCode method defined by class Object does return distinct
integers for distinct objects. (This is typically implemented by converting the internal address of the object
into an integer, but this implementation technique is not required by the Java™ programming language.)