Issue #65 has been updated by Jonathan Clarke.

Status changed from New to Assigned
Assigned to set to Jonathan Clarke
Target version set to 1.1.0

Hi Cl?ment, thanks for the report.

This error comes from the source bean not having any DN. DNs should come from 
either :
1) The source directory or DB (in the case of a DB, only if you have a field in 
your request that is named "distinguishName")
2) From the task properties dn rule.

I just committed a fix (bugs #47 and #64) that re-enables reading the DN from 
the source LDAP directory. So if you're using a ldap2ldap sync, this error 
should no longer happen with the latest lsc-core trunk (lsc-core-SNAPSHOT will 
be updated automatically during the night).

I'm about to commit a fix so that if the condition is false, we don't try to 
generate a DN (automatic generation uses the uid attribute from the source, 
which may not be present, thus the error), but set the DN to "No DN set! Read 
it from the source or set lsc.tasks.NAME.dn".

Please let me know if this fixes your bug, and if you think it's a good 
solution. Thanks!
----------------------------------------
Bug #65: Developpement error when using no create option
http://tools.lsc-project.org/issues/show/65

Author: Cl?ment Oudot
Status: Assigned
Priority: Normal
Assigned to: Jonathan Clarke
Category: Core
Target version: 1.1.0


Hello,

I make test on connectors, but when I use the "-nc" option, I have errors like 
this:

<pre>
     [java] 2355 [main] DEBUG  
org.lsc.AbstractSynchronize.synchronize2Ldap(AbstractSynchronize.java:331)   - 
Synchronizing org.lsc.objects.user for XXXX
     [java] 2386 [main] ERROR  
org.lsc.AbstractSynchronize.logActionError(AbstractSynchronize.java:477)   - 
Error while synchronizing ID XXXX: java.lang.RuntimeException: -- Development 
error: No RDN found (uid by default)!
     [java] java.lang.RuntimeException: -- Development error: No RDN found (uid 
by default)!
     [java]     at 
org.lsc.beans.BeanComparator.getAddEntry(BeanComparator.java:406)
     [java]     at 
org.lsc.beans.BeanComparator.calculateModifications(BeanComparator.java:165)
     [java]     at 
org.lsc.AbstractSynchronize.synchronize2Ldap(AbstractSynchronize.java:397)
     [java]     at 
org.lsc.SimpleSynchronize.launchTask(SimpleSynchronize.java:280)
     [java]     at org.lsc.SimpleSynchronize.launch(SimpleSynchronize.java:172)
     [java]     at org.lsc.Launcher.run(Launcher.java:128)
     [java]     at org.lsc.Launcher.main(Launcher.java:111)
</pre>

I have to say that my task does not have a dn rule because I just use the 
connector for updates. So I have these conditionnal rules:

<pre>
lsc.tasks.XXXX.condition.create = false
lsc.tasks.XXXX.condition.update = true
lsc.tasks.XXXX.condition.delete = false
lsc.tasks.XXXX.condition.modrdn = false
</pre>

The connector runs fine if I don't use "-nc" option.


-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090610/44783611/attachment.htm>

Reply via email to