You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2021/03/01 09:30:00 UTC

[jira] [Updated] (ISIS-2555) EntityChanges (as consumed by EntityChangesSubscriber) should associate with transaction, not interaction?

     [ https://issues.apache.org/jira/browse/ISIS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood updated ISIS-2555:
--------------------------------------
    Summary: EntityChanges (as consumed by EntityChangesSubscriber) should associate with transaction, not interaction?  (was: EntityChangesSubscriber should associate with transaction, not interaction?)

> EntityChanges (as consumed by EntityChangesSubscriber) should associate with transaction, not interaction?
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-2555
>                 URL: https://issues.apache.org/jira/browse/ISIS-2555
>             Project: Isis
>          Issue Type: Improvement
>          Components: Isis Core
>            Reporter: Daniel Keir Haywood
>            Priority: Minor
>             Fix For: 2.0.0-M6
>
>
> The docs say that EntityChanges has a uniqueId relating to a transaction, but I suspect it relates to the Interaction.  We do have a TransactionId that adds in a sequence (multiple transactions per interaction), so I think that EntityChanges should probably reference that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)