myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Andraschko (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Comment Edited] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet
Date Wed, 30 Sep 2015 11:52:05 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936743#comment-14936743
] 

Thomas Andraschko edited comment on MYFACES-3981 at 9/30/15 11:51 AM:
----------------------------------------------------------------------

The patch looks fine but will it also work correctly with a EL 2.x implementation?
If the property can't be resolved from the scopedMap, the ImportHandler would be still called
but doesn't exist in a EL 2.x environment. Maybe we would need a if(el==3.x) around the ImportHandler
stuff.


was (Author: tandraschko):
The patch looks fine but will it also work correctly with a EL 2.x implementation?

> 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-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)

Mime
View raw message