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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on SYNCOPE-1674:
----------------------------------------------------------

Commit 56ebaf2aac6c9f5c38643ad8ad7049494e7ff1d3 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=56ebaf2aac ]

[SYNCOPE-1674] Optimizing User, Group and Any Object lifecycle event publishing


> 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)