You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@causeway.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2023/03/26 12:25:00 UTC

[jira] [Updated] (CAUSEWAY-2639) [kroviz] Incoming Events Update Object as well as Lists (containing the Object)

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

Daniel Keir Haywood updated CAUSEWAY-2639:
------------------------------------------
    Fix Version/s:     (was: 2.0.0-RC2)

> [kroviz] Incoming Events Update Object as well as Lists (containing the Object)
> -------------------------------------------------------------------------------
>
>                 Key: CAUSEWAY-2639
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-2639
>             Project: Causeway
>          Issue Type: Improvement
>          Components: Incubator Client Kroviz
>            Reporter: Jörg Rade
>            Assignee: Jörg Rade
>            Priority: Major
>
> The state of the model-user interaction is kept in the EventStore. The ES logs all request/response pairs (LogEntry) and for each holds 1:n relations to Aggregtators.
> An Aggegator may be related to many LogEntries (resulting in m:n in total) and acts as a facade to the DisplayModel. DM's are rendered by views (RoDisplay). Incoming updates refresh the views.
> For kroviz the scenario you described boils down to: an updated entity may be part of an additional object list as well (and it's Aggregator/RoDisplay pair).
> There needs to be an (additional) relation between certain LogEntries and/or their Aggregators to handle this .
> See: https://the-asf.slack.com/archives/CFC42LWBV/p1619869133072400?thread_ts=1619867697.070300&cid=CFC42LWBV 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)