You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2022/05/07 15:18:00 UTC

[jira] [Updated] (SYNCOPE-1674) Optimize User, Group and Any Object lifecycle events management

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

Francesco Chicchiriccò updated SYNCOPE-1674:
--------------------------------------------
    Labels: elasticsearch  (was: )

> Optimize User, Group and Any Object lifecycle events management
> ---------------------------------------------------------------
>
>                 Key: SYNCOPE-1674
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1674
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core, extensions
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>              Labels: elasticsearch
>             Fix For: 2.1.12, 3.0.0
>
>
> There is already an existing mechanism to listen for User, Group and Any Object lifecycle events, based on Spring Framework's [event management features|https://docs.spring.io/spring-framework/docs/current/reference/html/core.html#context-functionality-events], introduced by SYNCOPE-1077 with purpose of keeping Elasticsearch indexes up to date with internal storage content.
> This mechanism can be improved by moving event publishing from persistence to workflow layer so that events are generated once for each high-level operation: a single workflow operation can in fact potentially generate multiple persistence operations.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)