Hi,
You can have 2 tasks, the first one filling uidNumber, and the second
one filling gidNumber based on uidNumber.
Regards,
Raphaël Ouazana.
Le 2016-07-22 03:39, Fong, Trevor a écrit :
Hi Everyone,
We're looking to use the same value for gidNumber and uidNumber.
We are following the approach outlined here:
http://lsc-project.org/wiki/documentation/2.0/configuration/syncoptions/sequences:
uidNumber calls method getNextValue
gidNumber calls method getCurrentValue
The problem is that the order of processing the attributes doesn't
seem to be guaranteed;
* if uidNumber is processed first, then gidNumber will have the same
value
* If gidNumber is processed first, then uidNumber will have the next
value
Is there a way to either:
* access the value of one <dataset> from another, or
* Write to a global variable
I noticed that there is a org.lsc.beans.OrderedValuesBean - will this
bean guarantee the order of execution of datasets? If so, in what
order - I've tried it and have noticed that the order it processes is
different from that specified in lsc.xml.
Thanks a lot,
Trev
_________________________________________________
TREVOR FONG
_Senior Programmer Analyst_
Information Technology | Engage. Envision. Enable.
THE UNIVERSITY OF BRITISH COLUMBIA
[email protected] | 1-604-827-5247 [1] | it.ubc.ca [2]
Links:
------
[1] tel:604-827-5247
[2] http://it.ubc.ca
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
