cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Gorshing (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-5903) Change TransportURIResolver to at least log exceptions
Date Thu, 24 Jul 2014 19:16:39 GMT
Chad Gorshing created CXF-5903:
----------------------------------

             Summary: 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: 3.0.1, 2.6.15
            Reporter: Chad Gorshing


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.2#6252)

Mime
View raw message