[seam-issues] [JBoss JIRA] Commented: (SEAMCATCH-26) Make caught exception available as named bean
[
https://issues.jboss.org/browse/SEAMCATCH-26?page=com.atlassian.jira.plug...
]
Jason Porter commented on SEAMCATCH-26:
---------------------------------------
Wondering if we need to make the CaughtException available (and at what point we do that,
it will change for each stack iteration) or if we just make the ExceptionStack available.
It should have every thing we need for org.jboss.seam.caughtException. Handled exception
we'd need to use each CaughtException if it's handled, not exactly sure if
that's what we want to do.
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
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