You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/11 13:05:00 UTC

[jira] [Commented] (ARIES-1926) UpdateSupport is changing effects execution order

    [ https://issues.apache.org/jira/browse/ARIES-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927540#comment-16927540 ] 

ASF subversion and git services commented on ARIES-1926:
--------------------------------------------------------

Commit a86ab9cf1bd3686ae96a4fa859d67a468cd23d86 in aries-component-dsl's branch refs/heads/master from Carlos Sierra
[ https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;h=a86ab9c ]

[ARIES-1926] UpdateSupport should not reorder effects

So publication of new event should happen after the termination of the
deferred terminators when running inside an upgrade operation.


> UpdateSupport is changing effects execution order
> -------------------------------------------------
>
>                 Key: ARIES-1926
>                 URL: https://issues.apache.org/jira/browse/ARIES-1926
>             Project: Aries
>          Issue Type: Bug
>          Components: Component DSL
>    Affects Versions: component-dsl-1.2.1
>            Reporter: Carlos Sierra
>            Priority: Major
>             Fix For: component-dsl-1.2.2
>
>
> When running as a result of an update operation, nodes with update support where reorganizing the effects because the termination was deferred but not the following adding event. This caused publication of the new event to happen before the termination of the previous event.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)