[ 
https://issues.apache.org/jira/browse/MYFACES-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Melloware resolved MYFACES-4548.
--------------------------------
    Resolution: Fixed

> Set default o.a.m.USE_LAMBDA_METAFACTORY to false
> -------------------------------------------------
>
>                 Key: MYFACES-4548
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4548
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.3-next-M7, 4.0.0-RC3
>            Reporter: Paul Nicolucci
>            Assignee: Melloware
>            Priority: Minor
>             Fix For: 2.3-next-M8, 4.0.0-RC4
>
>
> The default is currently true however, after discussion we're going to change 
> the default to false. The basis or this change is the following:
> {noformat}
> While looking over some code in MyFaces I noticed in Faces 4.0 we have the 
> following ELResolver:
> https://github.com/apache/myfaces/blob/main/impl/src/main/java/org/apache/myfaces/el/resolver/LambdaBeanELResolver.java
> This resolver is added to the resolver list here: 
> https://github.com/apache/myfaces/blob/main/impl/src/main/java/org/apache/myfaces/el/DefaultELResolverBuilder.java#L154
> Reading over the specification: 
> https://jakarta.ee/specifications/faces/4.0/jakarta-faces-4.0.html#a2966 I 
> wanted to 
> start a discussion on the following point in the specification:
> "These actual ELResolver instances must be added. It is not compliant to 
> simply add other resolvers that preserve these semantics."
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to