]
Brian Leathem commented on RF-13161:
------------------------------------
[~lfryc] +1. I've scheduled it to 4.3.4, and assigned it to you ;)
rich:notifyMessages CSS incorrect on MyFaces 2.x
------------------------------------------------
Key: RF-13161
URL:
https://issues.jboss.org/browse/RF-13161
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-output
Affects Versions: 4.2.3.Final, 4.2.4, 4.3.0.Final, 4.3.1, 4.3.2, 4.3.3
Reporter: John Yeary
Assignee: Lukáš Fryč
Labels: myfaces
Fix For: 4.3.4
Attachments: myfaces-rf-example.zip, myfaces-rf-example.zip,
RichfacesNotifyMessagesMyFaces.png
The FacesMessage Severity levels do not match between Mojarra and MyFaces. As a result,
the CSS styling for INFO messages are one level higher than they should be, and FATAL
messages are unstyled.
*Mojarra* - These represent values 0-3
{noformat}
/**
* <p>Array of all defined values, ascending order of ordinal value.
* Be sure you include any new instances created above, in the
* same order.</p>
*/
private static final Severity[] values =
{ SEVERITY_INFO, SEVERITY_WARN, SEVERITY_ERROR, SEVERITY_FATAL };
{noformat}
*MyFaces* - These represent values 1-4
{noformat}
/**
* Message severity level indicating an informational message rather than an error.
*/
public static final FacesMessage.Severity SEVERITY_INFO = new
Severity("Info", 1);
/**
* Message severity level indicating that an error might have occurred.
*/
public static final FacesMessage.Severity SEVERITY_WARN = new
Severity("Warn", 2);
/**
* Message severity level indicating that an error has occurred.
*/
public static final FacesMessage.Severity SEVERITY_ERROR = new
Severity("Error", 3);
/**
* Message severity level indicating that a serious error has occurred.
*/
public static final FacesMessage.Severity SEVERITY_FATAL = new
Severity("Fatal", 4);
{noformat}
The *<rich:messages/>* component behaves correctly, and may be used as an
alternative.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: