https://jax-ws.dev.java.net/issues/show_bug.cgi?id=566 Issue #|566
Summary|UnsupportedMediaException on remote server failure
Component|jax-ws
Version|2.1.4
Platform|All
OS/Version|All
URL|
Status|NEW
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P2
Subcomponent|runtime
Assigned to|issues@jax-ws
Reported by|mguennew
------- Additional comments from
mguennew@... Tue May 20 19:46:34 +0000 2008 -------
If using JAX-WS for the client side and the webservice server returns a HTTP
status code of 500 for an internal server error the HttpTransportPipe class
tries to read the content.
As usually a webservice sends back a HTML error page this fails with an
UnsupportedMediaException as the content type is then text/html instead of
text/xml for SOAP.
Due to some strange reason HttpTransportPipe.checkStatusCode explicitely
excludes HTTP status code 500 instead of throwing a ClientTransportException
with ClientMessage.HTTP_STATUS_CODE and the status code and error message.
This issue is related to 491 as the UnsupportedMediaException hides the real
cause, but instead of the purposed extension of the exception, a better fitting
one should be thrown like a ClientTransportException with
ClientMessage.HTTP_STATUS_CODE stating the status code and error message.
---------------------------------------------------------------------
To unsubscribe, e-mail:
issues-unsubscribe@...
For additional commands, e-mail:
issues-help@...
