Petals SE POJO

Technical errors should NOT be transformed to Fault, and even less SOAPFault

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.3.0
  • Fix Version/s: 2.4.0
  • Component/s: None
  • Security Level: Public
  • Environment:
    -

Issue Links

Activity

Hide
Victor NOËL added a comment - Wed, 15 Jul 2015 - 11:50:54 +0200

FaultException is moved to the POJO SE and always must contain a Document to represent the Fault.
This Document must respect the WSDL contract of the implemented service.

Show
Victor NOËL added a comment - Wed, 15 Jul 2015 - 11:50:54 +0200 FaultException is moved to the POJO SE and always must contain a Document to represent the Fault. This Document must respect the WSDL contract of the implemented service.
Hide
Victor NOËL added a comment - Fri, 22 May 2015 - 16:57:15 +0200

We must be careful because client code is susceptible to rely on FaultException (see PETALSCDK-134).

I think we should move it to the POJO SE and remove SOAP related things so that people can still throw this exception.
And maybe also the DocumentException as it enables to provide XML for the fault content!

Show
Victor NOËL added a comment - Fri, 22 May 2015 - 16:57:15 +0200 We must be careful because client code is susceptible to rely on FaultException (see PETALSCDK-134). I think we should move it to the POJO SE and remove SOAP related things so that people can still throw this exception. And maybe also the DocumentException as it enables to provide XML for the fault content!

People

Dates

  • Created:
    Fri, 22 May 2015 - 16:52:20 +0200
    Updated:
    Wed, 15 Jul 2015 - 13:42:57 +0200
    Resolved:
    Wed, 15 Jul 2015 - 13:42:57 +0200