org.apache.brooklyn.entity.database.postgresql

Class PostgreSqlNodeSaltImpl.ExecuteScriptEffectorBody

java.lang.Object

org.apache.brooklyn.core.effector.EffectorBody<java.lang.String>

org.apache.brooklyn.entity.database.postgresql.PostgreSqlNodeSaltImpl.ExecuteScriptEffectorBody

Enclosing class:

PostgreSqlNodeSaltImpl

public static class PostgreSqlNodeSaltImpl.ExecuteScriptEffectorBody
extends EffectorBody<java.lang.String>

Field Summary

Fields

Modifier and Type	Field and Description
static ConfigKey<java.lang.String>	SCRIPT

Constructor Summary

Constructors

Constructor and Description
ExecuteScriptEffectorBody()

Method Summary

Modifier and Type	Method and Description
java.lang.String	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

SCRIPT

public static final ConfigKey<java.lang.String> SCRIPT

Constructor Detail

ExecuteScriptEffectorBody

public ExecuteScriptEffectorBody()

Method Detail

call

public java.lang.String 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<java.lang.String>