Module jakarta.el
Package jakarta.el

Class ELResolver

java.lang.Object
jakarta.el.ELResolver
Direct Known Subclasses:
ArrayELResolver, BeanELResolver, BeanNameELResolver, CompositeComponentAttributesELResolver, CompositeELResolver, EmptyStringToNullELResolver, FacesResourceBundleELResolver, FlashELResolver, ImplicitObjectELResolver, ImportELResolver, ListELResolver, MapELResolver, NotFoundELResolver, OptionalELResolver, RecordELResolver, ResourceBundleELResolver, ResourceELResolver, ScopedAttributeELResolver, ScopedAttributeELResolver, StaticFieldELResolver, TypeConverter

public abstract class ELResolver extends Object
Enables customization of variable, property, method call, and type conversion resolution behavior for Jakarta Expression Language expression evaluation.

While evaluating an expression, the ELResolver associated with the ELContext is consulted to do the initial resolution of the first variable of an expression. It is also consulted when a . or [] operator is encountered.

For example, in the Jakarta Expression Language expression ${employee.lastName}, the ELResolver determines what object employee refers to, and what it means to get the lastName property on that object.

Most methods in this class accept a base and property parameter. In the case of variable resolution (e.g. determining what employee refers to in ${employee.lastName}), the base parameter will be null and the property parameter will always be of type String. In this case, if the property is not a String, the behavior of the ELResolver is undefined.

In the case of property resolution, the base parameter identifies the base object and the property object identifies the property on that base. For example, in the expression ${employee.lastName}, base is the result of the variable resolution for employee and property is the string "lastName". In the expression ${y[x]}, base is the result of the variable resolution for y and property is the result of the variable resolution for x.

In the case of method call resolution, the base parameter identifies the base object and the method parameter identifies a method on that base. In the case of overloaded methods, the paramTypes parameter can be optionally used to identify a method. The paramsparameter are the parameters for the method call, and can also be used for resolving overloaded methods when the paramTypes parameter is not specified.

In the case of type conversion resolution, the obj parameter identifies the source object and the targetType parameter identifies the target type the source to covert to.

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 CompositeELResolvers, to define rich semantics for evaluating an expression.

For the getValue(jakarta.el.ELContext, java.lang.Object, java.lang.Object), getType(jakarta.el.ELContext, java.lang.Object, java.lang.Object), setValue(jakarta.el.ELContext, java.lang.Object, java.lang.Object, java.lang.Object), and isReadOnly(jakarta.el.ELContext, java.lang.Object, java.lang.Object) methods, an ELResolver is not responsible for resolving 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.

Similarly, for the convertToType(jakarta.el.ELContext, java.lang.Object, java.lang.Class<T>) method an ELResolver must set the propertyResolved to true to indicate that it handles the conversion of the object to the target type.

The getCommonPropertyType(jakarta.el.ELContext, java.lang.Object) method is primarily designed for design-time tool support, but must handle invocation at runtime as well. The Beans.isDesignTime() method can be used to determine if the resolver is being consulted at design-time or runtime.

Since:
Jakarta Server Pages 2.1
See Also: