Package org.bonitasoft.engine.expression

Class DocumentListReferenceExpressionExecutorStrategy

java.lang.Object

org.bonitasoft.engine.expression.NonEmptyContentExpressionExecutorStrategy

org.bonitasoft.engine.expression.DocumentListReferenceExpressionExecutorStrategy

All Implemented Interfaces:

ExpressionExecutorStrategy

public class DocumentListReferenceExpressionExecutorStrategy
extends NonEmptyContentExpressionExecutorStrategy

Author:

Baptiste Mesta, Matthieu Chaffotte, Celine Souchet

Field Summary

Fields 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

Constructors

Constructor	Description
DocumentListReferenceExpressionExecutorStrategy(DocumentService documentService, ActivityInstanceService activityInstanceService, ProcessDefinitionService processDefinitionService, ProcessInstanceService processInstanceService)

Method Summary

Modifier and Type	Method	Description
List<Object>	evaluate(List<SExpression> expressions, Map<String,Object> context, Map<Integer,Object> resolvedExpressions, ContainerState containerState)
Object	evaluate(SExpression expression, Map<String,Object> context, Map<Integer,Object> resolvedExpressions, ContainerState containerState)
ExpressionKind	getExpressionKind()
boolean	mustPutEvaluatedExpressionInContext()	Should we put the evaluated expressions of this strategy in the evaluation context?

Methods inherited from class org.bonitasoft.engine.expression.NonEmptyContentExpressionExecutorStrategy

validate

Methods inherited from class java.lang.Object

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

Constructor Details

DocumentListReferenceExpressionExecutorStrategy

public DocumentListReferenceExpressionExecutorStrategy(DocumentService documentService,
 ActivityInstanceService activityInstanceService,
 ProcessDefinitionService processDefinitionService,
 ProcessInstanceService processInstanceService)

Method Details

evaluate

public Object evaluate(SExpression expression,
 Map<String,Object> context,
 Map<Integer,Object> resolvedExpressions,
 ContainerState containerState)
                throws SExpressionEvaluationException,
SExpressionDependencyMissingException

Parameters:

expression - the expression to evaluate

context - map containing the result of the evaluation of dependencies and also informations about the context of evaluation given by ExpressionExecutorStrategy.CONTAINER_ID_KEY and ExpressionExecutorStrategy.CONTAINER_TYPE_KEY

Returns:

the result of the evaluation of the expression of appropriate type

Throws:

SExpressionEvaluationException

SExpressionDependencyMissingException

getExpressionKind

public ExpressionKind getExpressionKind()

evaluate

public List<Object> evaluate(List<SExpression> expressions,
 Map<String,Object> context,
 Map<Integer,Object> resolvedExpressions,
 ContainerState containerState)
                      throws SExpressionEvaluationException,
SExpressionDependencyMissingException

Throws:

SExpressionEvaluationException

SExpressionDependencyMissingException

mustPutEvaluatedExpressionInContext

public boolean mustPutEvaluatedExpressionInContext()

Description copied from interface: ExpressionExecutorStrategy

Should we put the evaluated expressions of this strategy in the evaluation context?