-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: 5.0.2
-
Fix Version/s: 5.1.0 GA
-
Component/s: Documentation, JBossESB
-
Labels:
-
Environment:
n/a (documentation issue)
-
Affects:Documentation (Ref Guide, User Guide, etc.)
-
Estimated Difficulty:High
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
The documentation of the wise SOAPClient does not specify it's behaviour when the web service being called generates a SOAP fault. In actuality, the SOAPClient throws an ActionProcessingException with the SOAP fault as actual fault. This should at least be documented in the SOA-P programmers guide. It should also be mentioned that by default this error will not be returned when being called via SOAP ourselves (see below), and that there will be no redelivery when being called via JMS (since it's not a RuntimeException).
This default behaviour does cause problems when using the SOAPClient within an ESB-published web service endpoint itself. Apparently the "faultTo" EPR doesn't get set for exposed web service end points (which might be intended, or a different defect).
See https://access.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=1178003 for discussion.
