[
https://issues.apache.org/jira/browse/SYNCOPE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578402#comment-13578402
]
Hudson commented on SYNCOPE-307:
--------------------------------
Integrated in Syncope-trunk #89 (See
[https://builds.apache.org/job/Syncope-trunk/89/])
SYNCOPE-307: virtual attribute values must be retrieved before the
propByRes purge - merged from branch 1_0_X (Revision 1446200)
Result = SUCCESS
fmartelli :
Files :
* /syncope/trunk
*
/syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java
> 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
