Issue #47 has been updated by J?r?me Schell.
> > J?r?me - This may mean that there is no DN for that object in your source. If > you're going a db2ldap sync, that's likely. I've tried with db2ldap and ldap2ldap. Same problem, the result is null. > Do you need to access the dstBean DN ? Or the generated DN from the > lsc.tasks.TASKNAME.dn property ? > > Let me know which, because we may need to make the generated DN accessible. Huum, not sure to get it right :) I just need the DN of the entry being synchronized that's why I was using soc.getDistinguishName(). Nevertheless I solved this issue by constructing myself the DN but I thought that this method should return a valid result too ;) ---------------------------------------- Bug #47: srcBean.getDistinguishName does not works like expected http://tools.lsc-project.org/issues/show/47 Author: Cl?ment Oudot Status: Feedback Priority: Normal Assigned to: Cl?ment Oudot Category: Core Target version: 1.1.0 Hello, I try to use this to select branches : <pre> lsc.tasks.inetOrgPerson.condition.create = srcBean.getDistinguishName().toLowerCase().matches(".*((ou=users)|(ou=admin)).*") </pre> but the result of srcBean.getDistinguishName() is the generated DN and not the orginal DN, so the test does not work. But when looking in log, we see the wanted DN because the logger use "id". -- 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/20090603/2158d959/attachment-0001.htm>
