Petals CDK

Move flow attributes responsibility to CDK

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.4.2
  • Fix Version/s: 5.5.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Currently, flow attributes are initialised in a new exchange in the implementation of the MessageExchangeFactory present in the container (petals-message-exchange).

    Since most of the work around flow attributes is actually done in the CDK, it would be more coherent to move this initialisation in the CDK (at exchange creation).

    Note:

    There is code responsibility: for now flow attributes things are implemented in petals-log, petals-commons-log and petals-cdk-steplog
    There runtime responsibility: for now flow attributes are initialised in messages in the container, and manipulated (transferred from message to execution context) in the CDK

    This issue concerns the second point.

    See also PETALSESBCONT-328.

    Show
    Currently, flow attributes are initialised in a new exchange in the implementation of the MessageExchangeFactory present in the container (petals-message-exchange). Since most of the work around flow attributes is actually done in the CDK, it would be more coherent to move this initialisation in the CDK (at exchange creation). Note: There is code responsibility: for now flow attributes things are implemented in petals-log, petals-commons-log and petals-cdk-steplog There runtime responsibility: for now flow attributes are initialised in messages in the container, and manipulated (transferred from message to execution context) in the CDK This issue concerns the second point. See also PETALSESBCONT-328.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:04:30 +0200
Field Original Value New Value
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:10:55 +0200
Link This issue depends on PETALSESBCONT-328 [ PETALSESBCONT-328 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:21:01 +0200
Link This issue depends on PETALSESBCONT-328 [ PETALSESBCONT-328 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:21:38 +0200
Link This issue blocks PETALSESBCONT-328 [ PETALSESBCONT-328 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:25:52 +0200
Link This issue blocks PETALSESBCONT-329 [ PETALSESBCONT-329 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:26:21 +0200
Link This issue blocks PETALSESBCONT-329 [ PETALSESBCONT-329 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:57:50 +0200
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 10:57:52 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Thu, 23 Apr 2015 - 11:00:16 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.5.0 [ 10406 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
53m 25s
1
Victor NOËL
Thu, 23 Apr 2015 - 10:57:50 +0200
Open Open In Progress In Progress
2s
1
Victor NOËL
Thu, 23 Apr 2015 - 10:57:52 +0200
In Progress In Progress Resolved Resolved
2m 24s
1
Victor NOËL
Thu, 23 Apr 2015 - 11:00:16 +0200



People

Dates

  • Created:
    Thu, 23 Apr 2015 - 10:04:25 +0200
    Updated:
    Thu, 23 Apr 2015 - 11:00:16 +0200
    Resolved:
    Thu, 23 Apr 2015 - 11:00:16 +0200
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.