[ http://issues.apache.org/jira/browse/AXISCPP-726?page=comments#action_12314990 ]
Samisa Abeysinghe commented on AXISCPP-726: ------------------------------------------- Well we could add another method in addition to 'what()' method to extract the http specific error. However, in this case, the user must know that this is a Transport Exception in order to call 'cause' method, as it is does not make sense to have such a method at the base class level in AxisException class. So you will not be able to benefit from plymorphism :-( A better alternative would be to classify the sections of the error message such as: "Axis Client error: HTTP trasport error HTTP error: unauthorized" This way we could catch the excpetion using the base class and still be able to see the HTTP specific error. Thoughts please... > 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 > > 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
