StatusMessages: global messages not displayed in the right order ---------------------------------------------------------------- Key: JBSEAM-4557 URL: https://jira.jboss.org/jira/browse/JBSEAM-4557 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1, 2.1.1.GA Reporter: Yannick Lazzari Priority: Minor The StatusMessages component uses a HashMap to store keyed messages, i.e. messages added through the different addToControl methods. Because of that, when those messages are transferred to FacesMessages when rendering the response, they are added in a random order. Please modify the behaviour so that messages are transferred to the FacesMessages in the order in which they were added to StatusMessages (changing the HashMap for a LinkedHashMap for instance). I know that this shouldn't matter if you only display the error message next to the control, but if you also choose to display them with global messages, the order in which they are displayed is not the order in which they were added. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira