[
https://issues.apache.org/jira/browse/DELTASPIKE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645858#comment-13645858
]
Jason Porter commented on DELTASPIKE-357:
-----------------------------------------
Cast the exception event (or actually change the type on the parameter) to
IntrospectiveExceptionEvent and check the isBeforeTraversal method. If it's
true, return otherwise do what you need to do. You should find the order to be
what you expect in that case.
> ExceptionHandler should call exception hierarchies bottom up
> ------------------------------------------------------------
>
> Key: DELTASPIKE-357
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-357
> Project: DeltaSpike
> Issue Type: Bug
> Components: ExceptionControl-Module
> Affects Versions: 0.3-incubating
> Reporter: Maik Ebert
>
> I would assume that when you have an exception hierarchy DeltaSpike would
> call handlers for the sub class before it call handlers for the super class.
> But that's not the case.
> Assume you have:
> {code}
> @ExceptionHandler
> public class AdminWebExceptionHandler {
> public void handleAccessDeniedException(@Handles @FacesRequest
> ExceptionEvent<AccessDeniedException> exceptionEvent, FacesContext
> facesContext) {
> }
> public void handleRuntimeException(@Handles(ordinal = -1) @FacesRequest
> ExceptionEvent<RuntimeException> exceptionEvent, FacesContext facesContext) {
> }
> }
> {code}
> In that case handleRuntimeException() is called.
> I would except to have handleAccessDeniedException() called instead.
--
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
