[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2596) Exception handling - Never try to do anything after an exception but exception handling

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-2596?page=all ]

Gavin King closed JBSEAM-2596.
------------------------------

    Resolution: Rejected

This is simply not true. SeamPhaseListener does *not* swallow exceptions that occur during normal JSF phases, rather, they propagate to ExceptionFilter, and are handled there, outside of the JSF lifecycle.

The only time an exception gets swallowed by SeamPhaseListener is for exceptions that occur when processing page actions, page parameters, etc, but we have no choice about this because of the terrible exception handling behavior defined by the JSF spec for PhaseListeners. So this is the best we can do.

> Exception handling - Never try to do anything after an exception but exception handling
> ---------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-2596
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2596
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Shane Bryzak
>             Fix For: 2.1.0.GA
>
>
> This is related to JBSEAM-2595
> Currently, if no exception handler is defined
> for an exception, Seam will (after logging and swallowing in
> SeamPhaseListener) happily continue with the next phase. It WILL fall
> over and blow up with another exception in almost all cases,
> especially if the rendering triggers any database access. These are
> the famous "Transaction is not active" exceptions that THEN will
> appear on the page. There is no hint of the real cause, the swallowed
> exception. Not even a "check in the log, idiot" message. We need to
> figure out if the default exception handler (without pages.xml) as
> proposed in 1. is sufficient to solve this issue. I'm not sure about
> RENDER RESPONSE exceptions.

-- 
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