[
https://issues.apache.org/jira/browse/DELTASPIKE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482561#comment-13482561
]
Jason Porter commented on DELTASPIKE-165:
-----------------------------------------
I've been going back and forth on this one in my head because the original
event fired (ExceptionToCatchEvent) has a boolean flag indicating if the
exception was actually handled (isHandled). That should work fine if you're
sending the exception to catch yourself and any other integrations should be
able to do what is needed (for example JSF may want to bomb out if you're in
development mode so you can actually see what's going on). Will that work Ivo,
or would you still prefer the new event?
> Exception handlers: support handling unexpected exceptions
> ----------------------------------------------------------
>
> Key: DELTASPIKE-165
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-165
> Project: DeltaSpike
> Issue Type: Improvement
> Components: ExceptionControl-Module
> Reporter: Ivo Maixner
> Assignee: Jason Porter
>
> Provide a way to handle exceptions not handled by any other handler.
> Currently, a handler like this:
> public void unexpectedException(@Handles CaughtException<Throwable> event) {
> if (!event.isMarkedHandled()) {
> log.error("Unexpected exception", event.getException());
> messages.error(new BundleKey(MESSAGE_BUNDLE, "unexpected.exception"));
> }
> }
> gets in the way when there are other handlers which respond to non-root-cause
> exceptions.
> Some ideas:
> - an UnhandledException event fired as a last chance to handle it before
> re-throwing it as unhandled
> - a third traversal type - after BREADTH_FIRST and DEPTH_FIRST
> See https://community.jboss.org/thread/198408
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
