Hi all,
To add a little bit of information, as part of writing the @Inject
support it is also makes it possible to support #{facesContext} with
minimal effort. From a code perspective to have everything route through
the same CDI producer seems to make sense to me.
Obviously once we decide to do this with FacesContext more JSF artifacts
could easily follow the same route. But to keep the discussion focused I
just want to concentrate on FacesContext first.
Thanks,
Manfred
On 10/6/14, 10:43 AM, arjan tijms wrote:
> Hi,
>
> On Mon, Oct 6, 2014 at 5:20 PM, manfred riem<manfred.riem_at_oracle.com> wrote:
>> As part of the CDI alignment I think it is entirely feasible to have the CDI
>> runtime handle the EL resolving of #{facesContext}.
> As some background; it's currently handled (at least in Mojarra) by a
> custom EL resolver; com.sun.faces.el.ImplicitObjectELResolver
>
> The question would thus boil down to ELResolver vs CDI @Named (or
> extension equivalent). Haven't looked into the issue in depth, but
> things to consider might be the possibility to override the name or
> not and whether some order for resolving changes.
>
> Kind regards,
> Arjan