You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Thomas Andraschko (JIRA)" <de...@myfaces.apache.org> on 2018/03/11 09:41:00 UTC
[jira] [Commented] (MYFACES-4203) Verson 2.3.0 not compliant with
JSF spec 1102 on UIRepeat
[ https://issues.apache.org/jira/browse/MYFACES-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394469#comment-16394469 ]
Thomas Andraschko commented on MYFACES-4203:
--------------------------------------------
Did you really 2.3.0 or the beta version?
We had a similar issue and it was fixed: https://issues.apache.org/jira/browse/MYFACES-4131
> Verson 2.3.0 not compliant with JSF spec 1102 on UIRepeat
> ---------------------------------------------------------
>
> Key: MYFACES-4203
> URL: https://issues.apache.org/jira/browse/MYFACES-4203
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Assignee: Thomas Andraschko
> Priority: Major
> Fix For: 2.3.1
>
> Attachments: index.xhtml, myfaces-spec1102.diff
>
>
> As described at [https://github.com/javaee/javaserverfaces-spec/issues/1102] , UIRepeat should behave as c:forEach when given a begin and an end parameter, without any model.
> Mojarra impl already does that, as the deployment of the attached xhtml shows (althought it has some issues of her own on rerender).
> There's also a patch built on 2.3.0 version. Due to time restrictions, I couldn't make a unit test for the change, but the patched myfaces versions passes on all other tests and behaves on other jsf projects. Hope you can grab the changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)