[
https://issues.apache.org/jira/browse/SYNCOPE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573658#comment-13573658
]
fabio martelli commented on SYNCOPE-307:
----------------------------------------
Looking at the code I was thinking that a fast fix for this issue wouldn't be
so easy.
I can see just a solution: in case of the scenario in object, we have to
retrieve all virtual attribute values required.
Unfortunately this action is very expensive: virtual attribute values will be
searched remotely, on the external resources.
Since we already perform several connection towards one or more resource during
a synchronization (to retrieve before/after object, to create/update/delete, to
check availability, ....) I do think we have to avoid further useless
connection.
I would implement a very simple virtual attribute cache with the aim to reduce
a lot the number of query performed on the resources in order to retrieve
virtual attribute values. Whit this new feature I should fix this issue as well.
If no one will shout at me before tomorrow I will go on with this
idea/implementation.
> Virtual Attributes don't propagated in case of update during synchronization
> ----------------------------------------------------------------------------
>
> Key: SYNCOPE-307
> URL: https://issues.apache.org/jira/browse/SYNCOPE-307
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.6, 1.1.0
> Reporter: fabio martelli
> Assignee: fabio martelli
> Fix For: 1.0.6, 1.1.0
>
>
> UC:
> * Suppose two resources A and B;
> * Suppose to synchronize from A;
> * Suppose to have virtual attributes mapped just on B;
> * Suppose to retrieve a user to be updated locally and to be created new on B
> (thanks to an ad-hoc user template).
> User will be updated locally and created on B but its virtual attribute
> values won't be propagated on B.
> The bug is into the virtual attribute management during sync and propagation:
> in the UC provided above, the 'populate' method of the class
> AttributableOperations will never provide virtual attributes to be used by
> SyncJob to create the update propagation task.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
