[seam-issues] [JBoss JIRA] (SOLDER-153) Make caught exception available as named bean

[Bernard Labno (JIRA)]

    [ https://issues.jboss.org/browse/SOLDER-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669954#comment-12669954 ] 

Bernard Labno commented on SOLDER-153:
--------------------------------------

Jason, I think what we're hitting here is bug in WeldPhaseListener that destroys conversation context before error JSF does exception handling.
My poor workaround is to put ExceptionHandlerDispatch into Session scope. Drawback is that we see only most recent exception (if we were able to have handledException in conversation then we could create separate conversation per exception).
BTW. I was trying (inside handler) to check if conversation scope is active and if not then to activate it but the API overwhelmed me.
All in all I think that ExceptionHandlerDispatch is not a place for producing "handledException" and that other one or it should turn conversation context on if it's off.
                
> Make caught exception available as named bean
> ---------------------------------------------
>
>                 Key: SOLDER-153
>                 URL: https://issues.jboss.org/browse/SOLDER-153
>             Project: Solder
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Dan Allen
>            Assignee: Jason Porter
>            Priority: Minor
>             Fix For: 3.0.0.Beta2
>
>
> As we get into error pages, it's going to be useful to have the caught exception available via a named bean. I think this is just a matter of adding a dependent-scoped producer that reads the value of the current CaughtException from a field in the exception dispatcher.
> In Seam 2, the following two variables were available:
> org.jboss.seam.caughtException - the original exception that was caught
> org.jboss.seam.handledException - the exception cause currently being handled
> I think we could just map org.jboss.seam.caughtException to CaughtException...that way all the info is available, including the exception being handled, the original exception and the unwrapped stack.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira