[seam-issues] [JBoss JIRA] Resolved: (SEAMCATCH-26) Make caught exception available as named bean

[Jason Porter (JIRA)]

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

Jason Porter resolved SEAMCATCH-26.
-----------------------------------

    Resolution: Done


Fixed in 6bad0a0

> Make caught exception available as named bean
> ---------------------------------------------
>
>                 Key: SEAMCATCH-26
>                 URL: https://issues.jboss.org/browse/SEAMCATCH-26
>             Project: Seam Catch
>          Issue Type: Feature Request
>          Components: Core Implementation
>            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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira