public static class BrooklynNodeImpl.StopNodeButLeaveAppsEffectorBody extends EffectorBody<java.lang.Void> implements BrooklynNode.StopNodeButLeaveAppsEffector
| Modifier and Type | Field and Description |
|---|---|
static Effector<java.lang.Void> |
STOP_NODE_BUT_LEAVE_APPS |
TIMEOUT| Constructor and Description |
|---|
BrooklynNodeImpl.StopNodeButLeaveAppsEffectorBody() |
| Modifier and Type | Method and Description |
|---|---|
java.lang.Void |
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) |
public static final Effector<java.lang.Void> STOP_NODE_BUT_LEAVE_APPS
public BrooklynNodeImpl.StopNodeButLeaveAppsEffectorBody()
public java.lang.Void call(ConfigBag parameters)
EffectorBodyDynamicTasks 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.
call in class EffectorBody<java.lang.Void>