Issue #455 has been reported by Maxime Pelletier.
----------------------------------------
Bug #455: DefaultValue should not be calculated when the attribute already exist
http://tools.lsc-project.org/issues/455
Author: Maxime Pelletier
Status: New
Priority: Normal
Assigned to:
Category: Core
Target version:
Problem in version: 2.0
The same way as <createValue> is not calculated when the entry already exist,
<defaultValue> should not be calculated when the attribute already exist.
This if causing some problem when using the SequencesFactory as it increment
the nextValue of each entry synchronized.
A workaround is:
==========================
<dataset>
<name>uidNumber</name>
<policy>KEEP</policy>
<defaultValues>
<string>
(typeof(dstBean)=='undefined') ||
dstBean.getDatasetValuesById("uidNumber").equals('')?org.lsc.utils.SequencesFactory.getInstance(ldap.getJndiServices()).getNextValue("cn=uidNumberSequence,o=MYORG","serialNumber"):dstBean.getDatasetValuesById("uidNumber")
</string>
</defaultValues>
</dataset>
=======================
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
