axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Closed: (AXISCPP-726) Cannot retrieve the HTTP message from HTTPTransportException
Date Mon, 08 Aug 2005 09:41:39 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-726?page=all ]
     
Samisa Abeysinghe closed AXISCPP-726:
-------------------------------------

    Fix Version: 1.6 Alpha
     Resolution: Fixed

I changed the HTTP error code handling exception message to send something similr to the following:

 HTTPTransportException:HTTP transport error
 Server sent HTTP error: 'Not Found'

> Cannot retrieve the HTTP message from HTTPTransportException
> ------------------------------------------------------------
>
>          Key: AXISCPP-726
>          URL: http://issues.apache.org/jira/browse/AXISCPP-726
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture
>     Versions: current (nightly)
>     Reporter: Suresh Kumar
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.6 Alpha

>
> The axis code concatenates its own message text with the text from the HTTP messages
. For example, if there is a basic authentication failure,  it concatenates "HTTP transport
error" with "unauthorized". So, the caller sees the text "HTTP transport error unauthorized".
 There is no way  for the caller to know what the HTTP message was withouth parsing the exception
text.  The caller can take appropriate action based on the HTTP message. If the HTTP message
says "unauthorized" the operation can be aborted. Other wise (server down or some network
glitch)  the operation can be retried. So, it would be nice if the axis code returns its message
text and the HTTP text separately. Maybe there should  two "what()" methods, one returning
the axis text and the other the HTTP message text.
> This problem might be there for other types of exceptions also.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message