[
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949074#comment-14949074
]
Bill Lucy commented on MYFACES-3981:
------------------------------------
Thanks for the comments. What you've suggested [~lu4242] makes sense.. I've
attached a patch which takes those points into consideration: I added a
resolver that just extends our ScopedAttributeResolver, and is placed on the
resolver chain just before it. Usage of that new resolver
(ImportHandlerResolver) is gated on a custom property,
org.apache.myfaces.SUPPORT_EL_3_IMPORT_HANDLER, which is false by default. In
that resolver, EL 3.0 functionality is enabled via reflection.
Is this an appropriate property name, or do we want something more generic,
such as SUPPORT_EL_3, etc.? That could possibly allow us to gate future EL
"improvements" more easily.
> Unable to resolve Integer API as Lambda expression in a facelet
> ---------------------------------------------------------------
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-344
> Affects Versions: 2.2.7
> Reporter: Anup
> Priority: Minor
> Attachments: MYFACES-3981.patch, myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> <h:outputText id="out6" value="#{Integer.numberOfTrailingZeros(16)}"/>
> <h:outputText id="out7" value="#{((firstStr, secondStr)->
> (Integer.compare(firstInt,secondInt)))(5,6)}" />
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
