Metamer: rich:messages: doesn't display all messages (@globalOnly problem) -------------------------------------------------------------------------- Key: RF-11415 URL: https://issues.jboss.org/browse/RF-11415 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.1.0.Milestone2 Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79 Metamer 4.1.0.20110910-M2 r.unknown Mojarra 2.1.2-FCS Apache Tomcat 7.0.19 Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0 Reporter: Ján Jamrich Example page for rich:messages contains 2 messages (ok, really there are 3 messages components). First with @for, second with @globalOnly (to avoid interference between functionality of each of them). Then third rich:messages component is without any attribute set. Next, there is button on page which set couple of FacesMessages in actionListener method. Following FacesMessages are added to FacesContext: - 1 with SEVERITY_ERROR and without binding to any component (global) - 1 with SEVERITY_WARN and without binding to any component (global) - 2 with SEVERITY_ERROR, and bound to input1 and (second) to input2 - 2 with SEVERITY_WARN and bound to input1 and (second) to input2 When set attributes to following values: - @globalOnly=false - @for='' and click on button which generates FacesMessages, then expect in second messages (with attribute @globalOnly, and without @for attribute) all messages displayed (all messages bound to component + global messages since @globalOnly=false tells that we are not expecting only global messages). But in fact, there is displayed only one message - without binding to component (global). It mean we are missing all messages bound to some component, and secondly, we are missing messages with SEVERITY_WARN at all! What is important, in third rich:messages component without any attributes (except ID) are not displayed these messages as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira