[
https://issues.apache.org/jira/browse/CXF-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369462#comment-14369462
]
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: https://issues.apache.org/jira/browse/CXF-6198
> 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.
> https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=836b530ccf8b13f527169a0a4bd54a864762cb88;hb=refs/heads/master#l1566
> https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=7664129271bd6eb72d97a43c250355d5bd99ceb8;hb=refs/heads/2.7.x-fixes#l1558
> https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=836b530ccf8b13f527169a0a4bd54a864762cb88;hb=refs/heads/3.0.x-fixes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
