Petals ESB Container

Remove the UNKNOWN state for SAs and SUs

Details

  • Description:
    Hide

    According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs.

    The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see PETALSCDK-167), nevertheless, it is possible for the SU to throw an exception, but we consider the state is properly handled in that case (see PETALSCDK-166).

    Show
    According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs. The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see PETALSCDK-167), nevertheless, it is possible for the SU to throw an exception, but we consider the state is properly handled in that case (see PETALSCDK-166).
  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:07:47 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Minor [ 4 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:08:08 +0100
Link This issue depends on PETALSCDK-167 [ PETALSCDK-167 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:08:16 +0100
Link This issue depends on PETALSCDK-166 [ PETALSCDK-166 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:08:18 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Mon, 7 Mar 2016 - 16:15:00 +0100
Link This issue blocks PETALSDISTRIB-240 [ PETALSDISTRIB-240 ]
Victor NOËL made changes - Tue, 22 Mar 2016 - 15:47:58 +0100
Description According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs.

The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see PETALSCDK-167), so the only information the container has on the success or not of one of the lifecycle operation is in case of incoherent state (see PETALSCDK-166).

If this happens, it means there is a bug in the container (because we should avoid such situation to happen) and it should be logged as an error. 		According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs.

The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see PETALSCDK-167), nevertheless, it is possible for the SU to throw an exception, but we consider the state is properly handled in that case (see PETALSCDK-166).
Victor NOËL made changes - Tue, 22 Mar 2016 - 17:08:59 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.1 [ 10579 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Mon, 7 Mar 2016 - 16:07:39 +0100
    Updated:
    Tue, 22 Mar 2016 - 17:08:59 +0100
    Resolved:
    Tue, 22 Mar 2016 - 17:08:59 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.