Hi all,
I wanted to add more details about my email because I haven't
received any answer:)
The main problem behind this is that each time I run LSC, it
increments the next sequence value for each entry. Result: next value
is incremented by 10000 each time I run LSC. Doesn't make sense...
As a workaround, I did that:
==========================
<dataset>
<name>uidNumber</name>
<policy>KEEP</policy>
<defaultValues>
<string>
(typeof(dstBean)=='undefined') ||
dstBean.getDatasetValuesById("uidNumber").equals('')?org.lsc.utils.SequencesFactory.getInstance(ldap.getJndiServices()).getNe
xtValue("cn=uidNumberSequence,o=MYORG","serialNumber"):dstBean.getDatasetValuesById("uidNumber")
</string>
</defaultValues>
</dataset>
=======================
It's kind of over-complicated for somthing that should be simple.
Unless I someone tell me not to do it, I'll create a bug entry
about it today.
Regards
Maxime Pelletier <[email protected]> a écrit :
Hi,
I'm using the very nice SequenceFactory class in order to generate
uidNumber and gidNumber. In the wiki, it is suggested to setup the
attribute this way:
<dataset> <name>uidNumber</name> <policy>KEEP</policy>
<defaultValues>
<string>SequencesFactory.getInstance(ldap.getJndiServices()).
getNextValue("cn=uidNumberSequence,ou=Sequences,ou=HiddenTree,dc=lsc-project,dc=org", "serialNumber")</string>
</defaultValues>
</dataset>
However, the default value is calculated each time the task is ran
even if the attribute already exist.
You can fix that by setting it as a createValues but depending of
what you're doing, it might cause you some problems.
In short, I think that the defaults value shouldn't be calculated if
the attribute already exist in the destination. What do you think
about that? Should I open a bug about it?
Regards,
Maxime
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
