Class ConditionExpressionExecutorStrategy
java.lang.Object
org.bonitasoft.engine.expression.NonEmptyContentExpressionExecutorStrategy
org.bonitasoft.engine.expression.impl.ConditionExpressionExecutorStrategy
- All Implemented Interfaces:
ExpressionExecutorStrategy
- Author:
- Elias Ricken de Medeiros, Matthieu Chaffotte, Celine Souchet
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringFields inherited from interface org.bonitasoft.engine.expression.ExpressionExecutorStrategy
CONTAINER_ID_KEY, CONTAINER_TYPE_KEY, DEFINITION_ID, INTERPRETER_GROOVY, KIND_BUSINESS_DATA, KIND_BUSINESS_DATA_REFERENCE, KIND_BUSINESS_OBJECT_DAO, KIND_CONSTANT, KIND_CONTRACT_INPUT, KIND_DOCUMENT, KIND_DOCUMENT_LIST, KIND_ENGINE_CONSTANT, KIND_INPUT, KIND_JAVA_METHOD_CALL, KIND_LIST, KIND_PARAMETER, KIND_PATTERN, KIND_QUERY_BUSINESS_DATA, KIND_READ_ONLY_CONDITION_SCRIPT_GROOVY, KIND_READ_ONLY_SCRIPT_GROOVY, KIND_TRANSIENT_VARIABLE, KIND_VARIABLE, KIND_XPATH_READ, NO_DEPENDENCY_EXPRESSION_EVALUATION_ORDER, TYPE_BUSINESS_DATA, TYPE_BUSINESS_DATA_REFERENCE, TYPE_BUSINESS_OBJECT_DAO, TYPE_CONSTANT, TYPE_CONTRACT_INPUT, TYPE_DOCUMENT, TYPE_DOCUMENT_LIST, TYPE_ENGINE_CONSTANT, TYPE_INPUT, TYPE_JAVA_METHOD_CALL, TYPE_LIST, TYPE_PARAMETER, TYPE_PATTERN, TYPE_QUERY_BUSINESS_DATA, TYPE_READ_ONLY_CONDITION_SCRIPT, TYPE_READ_ONLY_SCRIPT, TYPE_TRANSIENT_VARIABLE, TYPE_VARIABLE, TYPE_XPATH_READ -
Constructor Summary
ConstructorsConstructorDescriptionConditionExpressionExecutorStrategy(LogicalComplementExecutor logicalComplementExecutor, BinaryComparatorExecutor binaryComparatorExecutor) -
Method Summary
Modifier and TypeMethodDescriptionevaluate(List<SExpression> expressions, Map<String, Object> context, Map<Integer, Object> resolvedExpressions, ContainerState containerState) evaluate(SExpression expression, Map<String, Object> context, Map<Integer, Object> resolvedExpressions, ContainerState containerState) booleanShould we put the evaluated expressions of this strategy in the evaluation context?voidvalidate(SExpression expression) Validate the expression, an exception is thrown it is invalid
-
Field Details
-
LOGICAL_COMPLEMENT_OPERATOR
- See Also:
-
NOT_EQUALS_COMPARATOR
- See Also:
-
EQUALS_COMPARATOR
- See Also:
-
GREATER_THAN_OR_EQUALS_COMPARATOR
- See Also:
-
lESS_THAN_OR_EQUALS_COMPARATOR
- See Also:
-
GREATER_THAN_COMPARATOR
- See Also:
-
LESS_THAN_COMPARATOR
- See Also:
-
-
Constructor Details
-
ConditionExpressionExecutorStrategy
public ConditionExpressionExecutorStrategy(LogicalComplementExecutor logicalComplementExecutor, BinaryComparatorExecutor binaryComparatorExecutor)
-
-
Method Details
-
evaluate
public Object evaluate(SExpression expression, Map<String, Object> context, Map<Integer, throws SExpressionEvaluationExceptionObject> resolvedExpressions, ContainerState containerState) - Parameters:
expression- the expression to evaluatecontext- map containing the result of the evaluation of dependencies and also informations about the context of evaluation given byExpressionExecutorStrategy.CONTAINER_ID_KEYandExpressionExecutorStrategy.CONTAINER_TYPE_KEY- Returns:
- the result of the evaluation of the expression of appropriate type
- Throws:
SExpressionEvaluationException
-
validate
Description copied from interface:ExpressionExecutorStrategyValidate the expression, an exception is thrown it is invalid- Specified by:
validatein interfaceExpressionExecutorStrategy- Overrides:
validatein classNonEmptyContentExpressionExecutorStrategy- Parameters:
expression- the expression to validate- Throws:
SInvalidExpressionException- if the exception is invalid
-
getExpressionKind
-
evaluate
public List<Object> evaluate(List<SExpression> expressions, Map<String, Object> context, Map<Integer, throws SExpressionEvaluationExceptionObject> resolvedExpressions, ContainerState containerState) - Throws:
SExpressionEvaluationException
-
mustPutEvaluatedExpressionInContext
public boolean mustPutEvaluatedExpressionInContext()Description copied from interface:ExpressionExecutorStrategyShould we put the evaluated expressions of this strategy in the evaluation context?
-