[
https://issues.apache.org/jira/browse/CXF-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-4241.
------------------------------
Resolution: Not A Problem
Assignee: Aki Yoshida
explained how the client endpoint can be configured to process soap faults with
http status other than 500.
> Http Conduit doesnt honor soap fault if server sends with 400 or 500 error
> --------------------------------------------------------------------------
>
> Key: CXF-4241
> URL: https://issues.apache.org/jira/browse/CXF-4241
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.4.6
> Environment: Linux;JDK 1.6.25
> Reporter: kanagamahendran Velusamy
> Assignee: Aki Yoshida
> Labels: conduit, http
>
> We have a situation where server sends Soap-fault with 400(http error)
> however cxf throws exception saying that "400: Bad Request" without the
> details of the message.
> my point is, even though server sends 400 or 500, CXF should read the message
> and if it is soap fault,it should construct soap fault not just the exception
> . in this way we are not restricting server to send the soap fault in 200 OK
> level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
