jsr344-experts@javaserverfaces-spec-public.java.net

[jsr344-experts] [1141-EL-3.0] Notification

From: Edward Burns <edward.burns_at_oracle.com>
Date: Fri, 15 Feb 2013 10:01:20 -0800

Hello Volunteers,

I've added some text to the spec to require enabling EL 3.0 if running
in a container that supports it. It's very simple. From [1]:

KC> place these ELResolvers
KC> between
KC> the custom ELResolvers and the MapELResolver.

KC> The ELResolver returned by ExpressionFactory.getStreamELResolver().
KC> javax.el.StaticFieldELResolver.

This manifests itself in the following spec modification.

M valueReferences.fm

- Update table 5-10, the diagram ELResolver for Facelets and
  Programmatic Access.

M FacesELResolverForFaces.png
M ELResolver.odg
M FacesELResolverForFaces.svg

- Update the actual diagram.

8<----------
5.6.2.8 Stream, StaticField, Map, List, Array, and Bean ELResolvers

These ELResolver instances are provided by the Unified EL API and must
be added in the following order:

[P1-start_EL_3_0] If running on a container that supports EL 3.0: The
return from ExpressionFactory.getStreamELResolver,
javax.el.StaticFieldELResolver. [P1-end_EL_3_0]

javax.el.MapELResolver, javax.el.ListELResolver,
javax.el.ArrayELResolver, javax.el.BeanELResolver. These actual
ELResolver instances must be added. It is not compliant to simply add
other resolvers that preserve these semantics.
8<----------

Ed

-- 
[1] http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1164