Affects: Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration
Complexity: High
Help Desk Ticket Reference: https://access.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=1178003
project_key: SOA

The SOAPUI client in JBoss ESB (org.jboss.soa.esb.actions.soap.SOAPClient) currently has the following behaviour when encountering a SOAP fault, and HTTP 500, in the web service being called:
- Print "WARN  [SOAPClient] Received status code '500' on HTTP SOAP (POST) request to ....."
- Ignore the fault and just continue to the next action
Besides the fact that this might be an inappropriate default, there are the following problems with the approach:
- It is completely undocumented (Programmers Guide 11.7.4 doesn't specify this)
- It is inconsistent with wise SOAPClient (which throws a ActionProcessingException in the same situation)

At least, please document the behaviour so clients know what to expect.
Better would be to align with wise client, and stop processing when a SOAP fault occurs (arguably a better default). Possibly do this through configuration option, if we don't want to break backwards compatibility).

Related to https://jira.jboss.org/browse/SOA-2186 .