- 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.