public abstract class ExplicitEffector<I,T> extends AbstractEffector<T>
Constructor and Description |
---|
ExplicitEffector(java.lang.String name,
java.lang.Class<T> type,
java.util.List<ParameterType<?>> parameters,
java.lang.String description) |
ExplicitEffector(java.lang.String name,
java.lang.Class<T> type,
java.lang.String description) |
Modifier and Type | Method and Description |
---|---|
T |
call(Entity entity,
java.util.Map parameters) |
static <I,T> ExplicitEffector<I,T> |
create(java.lang.String name,
java.lang.Class<T> type,
java.util.List<ParameterType<?>> parameters,
java.lang.String description,
groovy.lang.Closure body)
convenience to create an effector supplying a closure; annotations are preferred,
and subclass here would be failback, but this is offered as
workaround for bug GROOVY-5122, as discussed in test class CanSayHi
|
abstract T |
invokeEffector(I trait,
java.util.Map<java.lang.String,?> parameters) |
call, call, getBody
equals, getDescription, getName, getParameters, getReturnType, getReturnTypeName, hashCode, toString
getDescription, getName, getParameters, getReturnType, getReturnTypeName
public ExplicitEffector(java.lang.String name, java.lang.Class<T> type, java.lang.String description)
public ExplicitEffector(java.lang.String name, java.lang.Class<T> type, java.util.List<ParameterType<?>> parameters, java.lang.String description)
public T call(Entity entity, java.util.Map parameters)
call
in class AbstractEffector<T>
public abstract T invokeEffector(I trait, java.util.Map<java.lang.String,?> parameters)
public static <I,T> ExplicitEffector<I,T> create(java.lang.String name, java.lang.Class<T> type, java.util.List<ParameterType<?>> parameters, java.lang.String description, groovy.lang.Closure body)