[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2989) Log Seam FacesMessages with a filterable flag

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Wed Nov 5 21:55:21 EST 2008

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

Shane Bryzak reassigned JBSEAM-2989:

    Assignee: Dan Allen

> Log Seam FacesMessages with a filterable flag
> ---------------------------------------------
>                 Key: JBSEAM-2989
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2989
>             Project: Seam
>          Issue Type: Feature Request
>          Components: JSF Integration
>    Affects Versions: 2.0.1.CR1
>            Reporter: Pete Muir
>            Assignee: Dan Allen
>             Fix For: 2.1.1.CR1
> In general, Seam is over verbose in showing default messages to the end user. Most of these default messages has no real sense and should be rather logged at debug level to the log file. But we are forced to shown these messages if only we put h:message on the page :(.
> Currently this can be dealt with by overriding Seam's FacesMessages bean with higher precedence and dropping all Seam internal messages to file. Only messages added by my method addPublicMessage() are actually shown to end user.
> This realization is clumsy but it allows me to get rid of this unfortunate Seam's default behavior.
> As a solution we can add priorities like SEAM_INFO. Then you could filter these messages out in your custom FacesMessagesass. Seam would translate these to INFO at the view layer. Or some other flag you can access (to avoid overloading the meaning of priority). Perhaps also the ability to drop messages below a given priority.

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