[
https://issues.jboss.org/browse/SEAMCATCH-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572586#comment-12572586
]
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.
> Include the ability to filter stack traces
> ------------------------------------------
>
> Key: SEAMCATCH-4
> URL: https://issues.jboss.org/browse/SEAMCATCH-4
> Project: Seam Catch
> Issue Type: Feature Request
> Reporter: Jason Porter
> Assignee: Jason Porter
> Fix For: 3.0.0.Alpha4
>
>
> Catch should draw from ideas such as:
> -
> http://www.docjar.org/html/api/org/apache/commons/lang/exception/NestableDelegate.java.html
> -
> http://stackoverflow.com/questions/2504647/bash-how-to-filter-java-exception-info
> - http://squirrelsewer.blogspot.com/2010/03/filter-your-stack-traces.html
> - http://pastebin.com/p8aCSeuu
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
