-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.1.0 GA
-
Fix Version/s: 5.2.0.ER5
-
Component/s: JBossESB
-
Labels:None
-
Steps to Reproduce:
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
Wise will allow expected exceptions to be returned as an InvocationResult but will trap anything it does not recognise and throw it back to the invoker as an exception. This terminates the pipeline and the remainder of the pipeline is prevented from processing the valid SOAP response because wise is turning it into an exception, thereby treating it in a different manner from the exceptions that are defined within the WSDL (and expected). It is still visible through the exception processing but shouldn't be, it should be treated in the same manner as other SOAP faults.
- is blocked by
-
JBESB-3678 Wise SOAPFaultException processing relies on system property
-
- Closed
-
- is related to
-
JBESB-3643 WISE SOAPClient exception loss
-
- Closed
-
-
JBESB-3666 Smooks PropertyChecker can't find generated class
-
- Closed
-
- relates to
-
SOA-3227 Wise SOAPClient SOAPFaultException lost
-
- Closed
-