[
https://issues.jboss.org/browse/SOLDER-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668938#comment-12668938
]
Bernard Labno commented on SOLDER-153:
--------------------------------------
Jason, sorry, but this issue is not finished.
Take a look at Phase.java:
try {
handleAfterPhase(context, listeners, event);
} catch (Throwable e) {
queueException(context, e);
}
// stop timing
if (timer != null) {
timer.stopTiming();
timer.logResult(
"Execution time for phase (including any PhaseListeners)
-> "
+ this.getId().toString());
}
context.getExceptionHandler().handle();
Well, the conversation context will be ended on handleAfterPhase and
ExceptionHandlerDispatch.executeHandlers will be called on
context.getExceptionHandler().handle();
So I can't have the ExceptionHandlerDispatch moved to Conversation scope (even
with beans.xml modifications), cause the context won't be active.
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
