You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2015/01/21 13:30:34 UTC
[jira] [Resolved] (CXF-3344) Runtime Exceptions should not be
wrapped. Exceptions should not be logged and rethrown in
AbstractFaultChainInitiatorObserver
[ https://issues.apache.org/jira/browse/CXF-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved CXF-3344.
--------------------------------------
Resolution: Fixed
Removed the wrapping but keeping the logging as it might not be logged elsewhere
> Runtime Exceptions should not be wrapped. Exceptions should not be logged and rethrown in AbstractFaultChainInitiatorObserver
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-3344
> URL: https://issues.apache.org/jira/browse/CXF-3344
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Christian Schneider
> Assignee: Christian Schneider
>
> Currently the class org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver handles faults and sends them to a chain.
> If in this chain another exception occurs then three things happen.
> 1) The exception is Wrapped in a RuntimeException
> 2) The exception is logged
> 3) The exception is rethrown
> I propose to do the following instead :
> 1) Only Wrap the exception if it is no RuntimeException
> 2) Simply Rethrow and do not log as probably the Exception in caught and logged in another place anyway
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)