Details
Task
Resolved
Minor
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Priority | Blocker [ 1 ] | |
| Description |
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. |
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 |
| Link |
This issue blocks |
| Summary | Move flow attributes responsibility to CDK | Move flow attributes responsibility to CDK: Remove useless exchange builder |
| Description |
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 |
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. This implies that the complex architecture with the ContextualMessageExchangeImplBuilder is not needed anymore and can be removed. See also |
| Link |
This issue blocks |
| Link |
This issue depends on |
| Summary | Move flow attributes responsibility to CDK: Remove useless exchange builder | Remove useless contextual (related to flow attributes) exchange builder |
| Description |
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. This implies that the complex architecture with the ContextualMessageExchangeImplBuilder is not needed anymore and can be removed. See also |
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. This implies that the complex architecture with the ContextualMessageExchangeImplBuilder and AbstractContextualMessageExchangeFactory is not needed anymore and can be removed. See also |
| Link |
This issue blocks |
| Link |
This issue blocks |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Blocker [ 1 ] | Minor [ 4 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.0 [ 10413 ] | |
| Resolution | Fixed [ 1 ] |