[
https://issues.apache.org/jira/browse/CAMEL-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850313#comment-13850313
]
Mariusz Lotko commented on CAMEL-7071:
--------------------------------------
This is strange way to solve that. Should not we (application developers) use
exception wrapping?
Please note this method is used By ExchangeExceptionannotation.
> Exchange.getException(Class<T> clazz) returns root cause instead of thrown
> exception
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-7071
> URL: https://issues.apache.org/jira/browse/CAMEL-7071
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.12.2
> Reporter: Mariusz Lotko
> Assignee: Willem Jiang
>
> If I catch SQLException and wrap it in new MyCoolBuisinessException, then
> Exchange.getException() returns MyCoolBusinessException, but
> Exchange.getException(Exception.class) returns SQLException.
> This impacts ExchangeException annotation which calls
> Exchange.getException(Exception.class).
> Reason for that is in constructor of ObjectUtils.ExceptionIterator which for
> some reason calls Collections.reverse(tree).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
