You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org> on 2011/05/18 21:20:47 UTC

[jira] [Resolved] (MYFACES-3140) FacesMessage.VALUES is not ordered properly

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

Jakob Korherr resolved MYFACES-3140.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0-SNAPSHOT
                   2.0.6-SNAPSHOT
                   1.2.11-SNAPSHOT
                   1.1.10-SNAPSHOT

fixed in all branches

> FacesMessage.VALUES is not ordered properly
> -------------------------------------------
>
>                 Key: MYFACES-3140
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3140
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.1.9, 1.2.10, 2.0.5, 2.1.0-SNAPSHOT
>            Reporter: Matt Benson
>            Assignee: Jakob Korherr
>             Fix For: 1.1.10-SNAPSHOT, 1.2.11-SNAPSHOT, 2.0.6-SNAPSHOT, 2.1.0-SNAPSHOT
>
>         Attachments: MF-3140.patch.txt
>
>
> Per spec this list should be ordered as dictated by the ordinal values of the FacesMessage.Severity (emulated) enum values.  Attaching testcase proving it is not (additionally testing contract of VALUES_MAP) and patch to address issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira