cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5903) Change TransportURIResolver to at least log exceptions
Date Thu, 23 Mar 2017 13:56:42 GMT

     [ https://issues.apache.org/jira/browse/CXF-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-5903.
------------------------------
       Resolution: Fixed
         Assignee: Daniel Kulp
    Fix Version/s: 3.1.11
                   3.0.13
                   3.2.0

> Change TransportURIResolver to at least log exceptions
> ------------------------------------------------------
>
>                 Key: CXF-5903
>                 URL: https://issues.apache.org/jira/browse/CXF-5903
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.6.15, 3.0.1
>            Reporter: Chad Gorshing
>            Assignee: Daniel Kulp
>              Labels: easyfix
>             Fix For: 3.2.0, 3.0.13, 3.1.11
>
>
> In TransportURIResolver:resolve method, at the very end is a catch that ignores all exceptions.
What is the reasoning for this?
> I had some simple things wrong with a cxf.xml file (keystore path was incorrect), and
I did not receive any exception or error/warning of this. The exception that bubbled up does
have this information and was a valuable message, but nothing notified me of this case.
> Is it possible to at least add a log.error in this catch clause?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message