[ https://issues.apache.org/jira/browse/SYNCOPE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1705. --------------------------------------------- Resolution: Fixed > Deprecate SchedulingPullActions > ------------------------------- > > Key: SYNCOPE-1705 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1705 > Project: Syncope > Issue Type: Improvement > Components: core > Reporter: Francesco Chicchiriccò > Assignee: Francesco Chicchiriccò > Priority: Major > Fix For: 3.0.0-M2 > > > The class {{SchedulingPullActions}} has been used so far when, at the end of > a Pull Task's execution, some logic needed to be executed, which required the > entities pulled to be flushed to the internal storage. > Typical use case is > [LDAPMembershipPullActions|https://github.com/apache/syncope/blob/syncope-3.0.0-M1/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/pushpull/LDAPMembershipPullActions.java] > which, in its {{afterAll()}} method, is scheduling > [SetUMembershipsJob|https://github.com/apache/syncope/blob/syncope-3.0.0-M1/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/SetUMembershipsJob.java] > to update the pulled users so that they become members of the pulled groups, > matching the similar relationships existing in LDAP. > Such scheduling approach has proven to be problematic, especially because the > job scheduled at the end of a pull task execution cannot be controlled. -- This message was sent by Atlassian Jira (v8.20.10#820010)