Petals CDK

SU lifecycle operations should throw exceptions in case of failure

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 5.5.0
  • Fix Version/s: 5.6.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    According to the JBI specification, all the operation of the service unit lifecycle should throw exception in the following cases:

    • the SU is not deployed (except for deploy for which it is when an SU with the same name already exists).
    • incoherent state (except for deploy again).

    Nevertheless, in Petals, we consider that other reasons of failure are better reported through exceptions instead of being logged (it is easier for the container to find them and report them to the admin).

    Show
    According to the JBI specification, all the operation of the service unit lifecycle should throw exception in the following cases:
    • the SU is not deployed (except for deploy for which it is when an SU with the same name already exists).
    • incoherent state (except for deploy again).
    Nevertheless, in Petals, we consider that other reasons of failure are better reported through exceptions instead of being logged (it is easier for the container to find them and report them to the admin).
  • Environment:
    -

Issue Links

Activity

Hide
Victor NOËL added a comment - Mon, 7 Mar 2016 - 15:52:02 +0100

Add explanation for the need of an exception in deploy.

Show
Victor NOËL added a comment - Mon, 7 Mar 2016 - 15:52:02 +0100 Add explanation for the need of an exception in deploy.
Hide
Victor NOËL added a comment - Tue, 22 Mar 2016 - 15:46:35 +0100

updated the description/title.

Show
Victor NOËL added a comment - Tue, 22 Mar 2016 - 15:46:35 +0100 updated the description/title.

People

Dates

  • Created:
    Mon, 7 Mar 2016 - 15:43:01 +0100
    Updated:
    Tue, 22 Mar 2016 - 15:46:36 +0100
    Resolved:
    Mon, 7 Mar 2016 - 16:12:30 +0100