[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3348) StatusMessages discards all messages issued without a resource bundle key

Stefano Travelli (JIRA) jira-events at lists.jboss.org
Thu Aug 28 11:13:38 EDT 2008

     [ https://jira.jboss.org/jira/browse/JBSEAM-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefano Travelli updated JBSEAM-3348:

    Attachment: StatusMessage.patch

I propose the attached patch.

It reworks the way null or empty values are managed for the message bundle key.

I assume that a null or empty key means that the default message should be used.

Also, the default message is used if the resource bundle return an empty string for the key (which happens, btw).

> StatusMessages discards all messages issued without a resource bundle key
> -------------------------------------------------------------------------
>                 Key: JBSEAM-3348
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3348
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0.BETA1
>         Environment: Ubuntu 8.04, JVM 1.6.0_06, JBoss 4.2.2
>            Reporter: Stefano Travelli
>         Attachments: StatusMessage.patch
> This is a regression after JBSEAM-3318.
> StatusMessages.add(messageTemplate, params..) and StatusMessages.add(severity, messageTemplate, params..) delegate the message to add(severity, key, detailKey, messageTemplate, messageDetailTemplate, params..) with null for 'key'.
> However the code discards the message if key is null (or empty) so that no message is 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


More information about the seam-issues mailing list