[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2714) Detect swallowed exceptions

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Aug 30 08:46:38 EDT 2008

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

Pete Muir closed JBSEAM-2714.

    Resolution: Won't Fix

IMO it's better to wait for JSF2 which will include the ability to handle any exception that propagates through JSF.

> Detect swallowed exceptions
> ---------------------------
>                 Key: JBSEAM-2714
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2714
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Exception Handling
>            Reporter: Matt Drees
>            Priority: Minor
> Sometimes exceptions are swallowed by frameworks out of Seam's control (Facelets debug component, for example does this; see http://www.seamframework.org/Community/FetchingDataLazilyOnANewPage#comment9216).  However, a rollback may be triggered by the throwing of such an exception, due to the RollbackInterceptor.
> Because the exception is swallowed, the developer has no immediate indication that an error has occurred, yet the persistence context will be cleared.  It's a very frustrating experience, trust me.
> Could Seam use an interceptor to note when a (non-application) exception is thrown by a Seam component, and if it is not eventually handled by Seam's exception handler at the end of the request, trigger a warning & a stacktrace in the log?

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