[ https://issues.apache.org/jira/browse/SYNCOPE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1234. --------------------------------------------- Resolution: Fixed > SyncDelta pre-processing > ------------------------ > > Key: SYNCOPE-1234 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1234 > Project: Syncope > Issue Type: Improvement > Components: core > Reporter: Francesco Chicchiriccò > Assignee: Francesco Chicchiriccò > Fix For: 2.0.7, 2.1.0 > > > ConnId's > [SyncDelta|http://connid.tirasa.net/apidocs/1.4/org/identityconnectors/framework/common/objects/SyncDelta.html] > encapsulates the information about retrieved objects during pull. > The SyncDelta content can be seen then as the real starting point of the pull > process of a certain entry. > Currently, such instances can be modified by several > [PullActions|https://github.com/apache/syncope/blob/2_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/pushpull/PullActions.java]' > methods; such option was meant to allow flexibility when dealing with wicked > use cases. > For several scenarios, however, such kind of modification occurs too much > later in the process: we need to extract and separate the SyncDelta > pre-processing into a dedicated PullActions' method, to be invoked at the > very beginning. -- This message was sent by Atlassian JIRA (v6.4.14#64029)