Examples of CompositeELResolver

javax.el.CompositeELResolver
Maintains an ordered composite list of child ELResolvers. Though only a single ELResolver is associated with an ELContext, there are usually multiple resolvers considered for any given variable or property resolution. ELResolvers are combined together using a CompositeELResolver, to define rich semantics for evaluating an expression. For the {@link #getValue(ELContext,Object,Object)}, {@link #getType(ELContext,Object,Object)}, {@link #setValue(ELContext,Object,Object,Object)} and{@link #isReadOnly(ELContext,Object,Object)} methods, an ELResolver is not responsible forresolving all possible (base, property) pairs. In fact, most resolvers will only handle a base of a single type. To indicate that a resolver has successfully resolved a particular (base, property) pair, it must set the propertyResolved property of the ELContext to true. If it could not handle the given pair, it must leave this property alone. The caller must ignore the return value of the method if propertyResolved is false. The CompositeELResolver initializes the ELContext.propertyResolved flag to false, and uses it as a stop condition for iterating through its component resolvers. The ELContext.propertyResolved flag is not used for the design-time methods {@link #getFeatureDescriptors(ELContext,Object)} and{@link #getCommonPropertyType(ELContext,Object)}. Instead, results are collected and combined from all child ELResolvers for these methods.
org.activiti.engine.impl.javax.el.CompositeELResolver
Maintains an ordered composite list of child ELResolvers. Though only a single ELResolver is associated with an ELContext, there are usually multiple resolvers considered for any given variable or property resolution. ELResolvers are combined together using a CompositeELResolver, to define rich semantics for evaluating an expression. For the {@link #getValue(ELContext,Object,Object)}, {@link #getType(ELContext,Object,Object)}, {@link #setValue(ELContext,Object,Object,Object)} and{@link #isReadOnly(ELContext,Object,Object)} methods, an ELResolver is not responsible forresolving all possible (base, property) pairs. In fact, most resolvers will only handle a base of a single type. To indicate that a resolver has successfully resolved a particular (base, property) pair, it must set the propertyResolved property of the ELContext to true. If it could not handle the given pair, it must leave this property alone. The caller must ignore the return value of the method if propertyResolved is false. The CompositeELResolver initializes the ELContext.propertyResolved flag to false, and uses it as a stop condition for iterating through its component resolvers. The ELContext.propertyResolved flag is not used for the design-time methods {@link #getFeatureDescriptors(ELContext,Object)} and{@link #getCommonPropertyType(ELContext,Object)}. Instead, results are collected and combined from all child ELResolvers for these methods.
org.camunda.bpm.engine.impl.javax.el.CompositeELResolver
Maintains an ordered composite list of child ELResolvers. Though only a single ELResolver is associated with an ELContext, there are usually multiple resolvers considered for any given variable or property resolution. ELResolvers are combined together using a CompositeELResolver, to define rich semantics for evaluating an expression. For the {@link #getValue(ELContext,Object,Object)}, {@link #getType(ELContext,Object,Object)}, {@link #setValue(ELContext,Object,Object,Object)} and{@link #isReadOnly(ELContext,Object,Object)} methods, an ELResolver is not responsible forresolving all possible (base, property) pairs. In fact, most resolvers will only handle a base of a single type. To indicate that a resolver has successfully resolved a particular (base, property) pair, it must set the propertyResolved property of the ELContext to true. If it could not handle the given pair, it must leave this property alone. The caller must ignore the return value of the method if propertyResolved is false. The CompositeELResolver initializes the ELContext.propertyResolved flag to false, and uses it as a stop condition for iterating through its component resolvers. The ELContext.propertyResolved flag is not used for the design-time methods {@link #getFeatureDescriptors(ELContext,Object)} and{@link #getCommonPropertyType(ELContext,Object)}. Instead, results are collected and combined from all child ELResolvers for these methods.

Examples of org.camunda.bpm.engine.impl.javax.el.CompositeELResolver


    return elResolver;
  }


  protected ELResolver createElResolver() {
    CompositeELResolver elResolver = new CompositeELResolver();
    elResolver.add(new VariableScopeElResolver());


    if(beans != null) {
      // ACT-1102: Also expose all beans in configuration when using standalone engine, not
      // in spring-context
      elResolver.add(new ReadOnlyMapELResolver(beans));
    }


    elResolver.add(new ProcessApplicationElResolverDelegate());


    elResolver.add(new ArrayELResolver());
    elResolver.add(new ListELResolver());
    elResolver.add(new MapELResolver());
    elResolver.add(new ProcessApplicationBeanElResolverDelegate());


    return elResolver;
  }

View Full Code Here

Examples of org.camunda.bpm.engine.impl.javax.el.CompositeELResolver

 */
public class CdiExpressionManager extends ExpressionManager {


  @Override
  protected ELResolver createElResolver() {
    CompositeELResolver compositeElResolver = new CompositeELResolver();
    compositeElResolver.add(new VariableScopeElResolver());


    compositeElResolver.add(new CdiResolver());


    compositeElResolver.add(new ArrayELResolver());
    compositeElResolver.add(new ListELResolver());
    compositeElResolver.add(new MapELResolver());
    compositeElResolver.add(new BeanELResolver());


    return compositeElResolver;
  }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.