public abstract class AbstractNamedOperation extends Operation implements NamedOperation, IdentifiedDataSerializable
Modifier and Type | Field and Description |
---|---|
protected String |
name |
GENERIC_PARTITION_ID
Modifier | Constructor and Description |
---|---|
|
AbstractNamedOperation() |
protected |
AbstractNamedOperation(String name) |
Modifier and Type | Method and Description |
---|---|
String |
getName()
Returns the name of the distributed data structure.
|
protected void |
readInternal(ObjectDataInput in) |
protected void |
toString(StringBuilder sb)
A template method allows for additional information to be passed into the
Operation.toString() method. |
protected void |
writeInternal(ObjectDataOutput out) |
afterRun, beforeRun, executedLocally, getCallerAddress, getCallerUuid, getCallId, getCallTimeout, getConnection, getInvocationTime, getLogger, getNodeEngine, getOperationResponseHandler, getPartitionId, getReplicaIndex, getResponse, getService, getServiceName, getWaitTimeout, isUrgent, logError, onExecutionFailure, onInvocationException, onSetCallId, readData, returnsResponse, run, sendResponse, setCallerUuid, setNodeEngine, setOperationResponseHandler, setPartitionId, setReplicaIndex, setService, setServiceName, setValidateTarget, setWaitTimeout, toString, validatesTarget, writeData
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
getFactoryId, getId
readData, writeData
protected String name
protected AbstractNamedOperation(String name)
public AbstractNamedOperation()
public final String getName()
NamedOperation
getName
in interface NamedOperation
protected void writeInternal(ObjectDataOutput out) throws IOException
writeInternal
in class Operation
IOException
protected void readInternal(ObjectDataInput in) throws IOException
readInternal
in class Operation
IOException
protected void toString(StringBuilder sb)
Operation
Operation.toString()
method. So an Operation
subclass can override this method and add additional debugging content. The default implementation does nothing so
one is not forced to provide an empty implementation.
It is a good practice always to call the super.toString(stringBuffer) when implementing this method to make sure
that the super class can inject content if needed.Copyright © 2017 Hazelcast, Inc.. All Rights Reserved.