Clément OUDOT <[email protected]> a écrit :
Le 25 avril 2012 15:11, Maxime Pelletier
<[email protected]> a écrit :
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.
Maxime,
why don't you use createValues as you suggested in your first mail,
what's the problem with it?
Clément.
Hi Clément,
This would solve only a part of my problem because some entries are
created manually in LDAP without the uidNumber. I then need to
calculate uidNumber with my LSC job. CreateValue is only use for a new
entry, not for a new attribute of an existing entry (you know that I'm
sure :).
Second, I think that defaultValue behavior should be consistent
with createValue (not calculated if not needed). Well, I think I'll
open a bug about it and we could debate there if it's a real bug or not.
Thanks
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
