cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-6198) No SOAPFault for HTTP error code 400
Date Thu, 19 Mar 2015 15:00:56 GMT


Akitoshi Yoshida commented on CXF-6198:

My interpretation was that the server may return a SOAP fault with http 400 in SOAP 1.2 to
indicate the client error, but this is not an application soap fault that is processed and
mapped back to the corresponding fault.

I am not sure whether changing this behavior to process the HTTP 400 SOAP faults may introduce
a regression in some BP 1.x. SOAP 1.1 related TCK tests. BP 2.0 does seem to give any hint
on the correct behavior. If things are okay, we can decide how to introduce this feature.
(i.e. active for both soap 1.* or only for 1.2, etc).

Someone else also wants to comment?

> No SOAPFault for HTTP error code 400
> ------------------------------------
>                 Key: CXF-6198
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.0.3, 2.7.14
>            Reporter: Bartosz Baranowski
> Currently on HTTP.500 is accessible as SOAPFAult, 400 cause exception.

This message was sent by Atlassian JIRA

View raw message