Petals BC SOAP

SOAP Fault should be properly transformed to Fault or Error

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.4.0
Fix Version/s: 5.0.1
Component/s: None
Security Level: Public

Description:

Hide

Currently, when receiving a SOAP Fault from an external SOAP provider (as a response to a message sent from a SOAP BC Provider thus), the Fault is transformed to a JBI Fault (see ~~PETALSBCSOAP-145~~).

But JBI Fault are meant to contain modelled faults (those declared in the WSDL), hence, we should check if the received fault is actually a modelled fault, and if not, we should transform the SOAP Fault into a JBI Error.

Show
Currently, when receiving a SOAP Fault from an external SOAP provider (as a response to a message sent from a SOAP BC Provider thus), the Fault is transformed to a JBI Fault (see ~~PETALSBCSOAP-145~~). But JBI Fault are meant to contain modelled faults (those declared in the WSDL), hence, we should check if the received fault is actually a modelled fault, and if not, we should transform the SOAP Fault into a JBI Error.

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSBCSOAP-145~~ JBI Errors should be transformed to SOAPFault

This issue blocks:
~~PETALSBCSOAP-78~~ the exception thrown on PetalsESB is different than the exception of the original webservice.
PETALSDISTRIB-133 Better management of errors versus faults in JBI exchanges

Activity

People

Assignee:

Christophe DENEUX

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Fri, 2 Oct 2015 - 17:33:58 +0200

Updated:

Wed, 3 Apr 2019 - 08:23:45 +0200

Resolved:

Wed, 3 Apr 2019 - 08:23:16 +0200