[ https://issues.jboss.org/browse/SEAMCATCH-4?page=com.atlassian.jira.plugi... ] Dan Allen commented on SEAMCATCH-4: ----------------------------------- I was thinking this could be quite useful for purging a stack trace for exceptions that simply don't need one. For instance, if the BeanManager can't be found, there is nothing in the stack trace that is really helping you there...it's a misconfiguration problem. Same would go for an XML file that can't be parsed. The message of the exception is really all you should need. The rest is just internal details. Obviously, this would be up to the discretion of the application writer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira