org.apache.brooklyn.entity.brooklynnode

Class BrooklynEntityMirrorImpl.RemoteEffector<T>

java.lang.Object

org.apache.brooklyn.core.effector.EffectorBody<T>

org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirrorImpl.RemoteEffector<T>

Enclosing class:

BrooklynEntityMirrorImpl

public static class BrooklynEntityMirrorImpl.RemoteEffector<T>
extends EffectorBody<T>

Field Summary

Fields

Modifier and Type	Field and Description
java.lang.String	remoteEffectorName
<any>	resultParser

Constructor Summary

Constructors

Constructor and Description
RemoteEffector(java.lang.String remoteEffectorName, <any> resultParser) creates an effector implementation which POSTs to a remote effector endpoint, optionally converting the byte[] response (if resultParser is null then null is returned)

Method Summary

Modifier and Type	Method and Description
T	call(ConfigBag parameters) Does the work of the effector, either in place, or (better) by building up subtasks, which can by added using DynamicTasks methods (and various convenience methods which do that automatically; see subclasses of EffectorBody for more info on usage; or see DynamicSequentialTask for details of the threading model by which added tasks are placed in a secondary thread)

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

remoteEffectorName

public final java.lang.String remoteEffectorName

resultParser

public final <any> resultParser

Constructor Detail

RemoteEffector

public RemoteEffector(java.lang.String remoteEffectorName,
                      @Nullable
                      <any> resultParser)

creates an effector implementation which POSTs to a remote effector endpoint, optionally converting the byte[] response (if resultParser is null then null is returned)

Method Detail

call

public T call(ConfigBag parameters)

Description copied from class: EffectorBody

Does the work of the effector, either in place, or (better) by building up subtasks, which can by added using DynamicTasks methods (and various convenience methods which do that automatically; see subclasses of EffectorBody for more info on usage; or see DynamicSequentialTask for details of the threading model by which added tasks are placed in a secondary thread)

The associated entity can be accessed through the EffectorBody.entity() method.

Specified by:

call in class EffectorBody<T>