[
https://issues.apache.org/jira/browse/CXF-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessio Soldano updated CXF-6198:
---------------------------------
Attachment: CXF-6198.diff
So, given there're still doubts on this, I believe the best approach is to do
what follows:
1) add an option for allowing processing responses on HTTP 400 response code
2) externalize the response code processing to a separate protected method that
can easily be overridden.
Attached you find a patch for doing that (and actually reading properties only
when needed). Unless someone see a valid reason for not going this way, I'll
commit the patch in the next days.
> 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
> Attachments: CXF-6198.diff
>
>
> 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)
