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

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

Commit f4b7a064127a89c06e148e8a5ecdd5daac7dda7f in syncope's branch 
refs/heads/1_2_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f4b7a06 ]

[SYNCOPE-936] Init token values from resource before proceeding


> Sync token reset to NULL when no SyncDelta items are available
> --------------------------------------------------------------
>
>                 Key: SYNCOPE-936
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-936
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.8, 2.0.0.M5
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.2.9, 2.0.0
>
>
> After SYNCOPE-855 that changed the whole handling of ConnId's {{SyncToken}}, 
> when no results (e.g. {{SyncDelta}} instances) are returned during 
> incremental synchronization, the external resource's sync tokens (stored for 
> next execution) are reset to NULL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to