ElValueProvider (Camunda Platform Javadocs 7.19.0-SNAPSHOT)

java.lang.Object
- org.camunda.bpm.engine.impl.el.ElValueProvider

All Implemented Interfaces:

Comparable<ElValueProvider>, ParameterValueProvider
```
public class ElValueProvider
extends Object
implements ParameterValueProvider, Comparable<ElValueProvider>
```
Makes it possible to use expression in IoParameter mappings.

Author:

Daniel Meyer

Field Summary

Fields
Modifier and Type Field Description

protected Expression expression

Constructor Summary

Constructors
Constructor Description

ElValueProvider(Expression expression)

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method	Description
`int`	`compareTo(ElValueProvider o)`
`Expression`	`getExpression()`
`Object`	`getValue(VariableScope variableScope)`
`boolean`	`isDynamic()`
`void`	`setExpression(Expression expression)`

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - expression
```
protected Expression expression
```
- Constructor Detail
  - ElValueProvider
```
public ElValueProvider(Expression expression)
```
- Method Detail
  - getValue
```
public Object getValue(VariableScope variableScope)
```
    Specified by:
    
    getValue in interface ParameterValueProvider
    
    Parameters:
    
    variableScope - the scope in which the value is to be resolved.
    
    Returns:
    
    the value
  - getExpression
```
public Expression getExpression()
```
  - setExpression
```
public void setExpression(Expression expression)
```
  - compareTo
```
public int compareTo(ElValueProvider o)
```
    Specified by:
    
    compareTo in interface Comparable<ElValueProvider>
  - isDynamic
```
public boolean isDynamic()
```
    Specified by:
    
    isDynamic in interface ParameterValueProvider
    
    Returns:
    
    true if the value provider:
    
    Can return a different value depending on the passed variable scope
    May uses external data for its resolution
    May have side effects
    If true, a caller of ParameterValueProvider.getValue(VariableScope) can assume that:
    
    passing an empty variable scope returns the same value as passing any other variable scope
    Calling ParameterValueProvider.getValue(VariableScope) multiple times always returns the same value
    Calling ParameterValueProvider.getValue(VariableScope) does not have side effects