Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <879232370.1258421259575.JavaMail.jira@brutus>
Date: Tue, 17 Nov 2009 01:27:39 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Resolved: (CXF-2537) Proposal : enhancement of HTTP
 exceptions messages
In-Reply-To: <655910833.1258385019670.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Kulp resolved CXF-2537.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.6
                   2.1.9


I made a slight change to the patch to make an attempt to keep the same exception type.  (SocketTimeoutException remains a SocketTimeoutException instead of a generic IOException).

> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
>                 Key: CXF-2537
>                 URL: https://issues.apache.org/jira/browse/CXF-2537
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 2.2.3
>            Reporter: Cyrille Le Clerc
>            Assignee: Daniel Kulp
>             Fix For: 2.1.9, 2.2.6
>
>         Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
>   ** Current message : java.io.IOException: Not Found
>   ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> 	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> 	at $Proxy67.sayHi(Unknown Source)
> 	...
> 	at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> 	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> 	... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> 	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> 	at $Proxy67.sayHi(Unknown Source)
> 	...
> 	at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> 	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> 	... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> 	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> 	... 71 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.