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

[ http://jira.jboss.com/jira/browse/JBSEAM-2515?page=comments#action_12406723 ] Przemyslaw Jaskierski commented on JBSEAM-2515: ----------------------------------------------- Pete, I guess overriding works (never used it though). Problem is that it is limited to showing generic messages only which were meant for i.e. log-in event or failed transaction. Generic "failed transaction"-like message has no real value/meaning for end user. And there is no strict control on what is shown to user (all these illegal navigation etc he has no clue about). Your (3) solution is great and very flexible. Another approach to priorities (in contrary to the JSF model) would be to be consistent to Seam components precedence model, all default Seam messages could have SEAM_BUILT_IN priority (with this as a default value, to make it quick to use). Priorities will allow to have an ability to silence all Seam messages in production but keep them for development/prototyping. Let developer decide what he wants to show. -- 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