[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2515) Abstraction of FacesMessages

[ http://jira.jboss.com/jira/browse/JBSEAM-2515?page=comments#action_12406682 ] Przemyslaw Jaskierski commented on JBSEAM-2515: ----------------------------------------------- Pete, Because looks like you're focusing on this class now, may I suggest something? In general, Seam is over verbose in showing default messages to the end user. I mean similarities of "Transaction failed", despite the fact that I actually show perfectly precise and meaningful message to 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 :(. Overriding default messages in resources solves nothing here... Currently I'm dealing with it 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. Can I suggest following? 1. Either allow to disable default Seam-internals-originated messages (and simply allow them to be logged). Provide a mean to ensure that only messages explicitly produced by developer are shown to user. or 2. Cross-redirect message preserving in FacesMessages is cool but these methods are private, make addToTasks*() and getTasks*() overrideable, and keep FacesMessages easy overrideable in general. TIA Regards, Przemek. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira