Adding, Deleting already existing account on dead resource generates reconciliation errors.

Consistency test scenario #14.

Prerequisites:

• OpenDJ stopped
• account with dn: uid=c,ou=People,dc=example,dc=com existing
• midPoint user nor account "c" existing

Steps:
(1) create user "c": name=fullname=familyname=c, assigned account on OpenDJ + Save
(2) start OpenDJ
(3) run reconciliation

Although the "c" user is reconciled OK (the result is that account "c" on OpenDJ is linked to midPoint user "c"), in the log there are spurious error messages:

2012-12-07 17:39:26,406 [RESOURCEOBJECTCHANGELISTENER] [midPointScheduler_Worker-9] ERROR (com.evolveum.midpoint.model.sync.SynchronizationService): ### SYNCHRONIZATION # notifyChange(..): Synchronization action failed, reason: Couldn't synchronize user, reason: com.evolveum.midpoint.util.exception.ObjectAlreadyExistsException: Could't add object. Object already exist, Account already exists on the resource: javax.naming.NameAlreadyBoundException([LDAP: error code 68 - The entry uid=c,ou=people,dc=example,dc=com cannot be added because an entry with that name already exists])
2012-12-07 17:39:26,406 [RESOURCEOBJECTCHANGELISTENER] [midPointScheduler_Worker-9] ERROR (com.evolveum.midpoint.provisioning.impl.ChangeNotificationDispatcherImpl): Exception class com.evolveum.midpoint.util.exception.SystemException thrown by object change listener model synchronization service: com.evolveum.midpoint.util.exception.SystemException: Synchronization action failed, reason: Couldn't synchronize user, reason: com.evolveum.midpoint.util.exception.ObjectAlreadyExistsException: Could't add object. Object already exist, Account already exists on the resource: javax.naming.NameAlreadyBoundException([LDAP: error code 68 - The entry uid=c,ou=people,dc=example,dc=com cannot be added because an entry with that name already exists])
com.evolveum.midpoint.util.exception.SystemException: com.evolveum.midpoint.util.exception.SystemException: Synchronization action failed, reason: Couldn't synchronize user, reason: com.evolveum.midpoint.util.exception.ObjectAlreadyExistsException: Could't add object. Object already exist, Account already exists on the resource: javax.naming.NameAlreadyBoundException([LDAP: error code 68 - The entry uid=c,ou=people,dc=example,dc=com cannot be added because an entry with that name already exists])
at com.evolveum.midpoint.model.sync.SynchronizationService.notifyChange_aroundBody0(SynchronizationService.java:155) ~[model-impl-2.1-SNAPSHOT.jar:na]
at com.evolveum.midpoint.model.sync.SynchronizationService$AjcClosure1.run(SynchronizationService.java:1) ~[model-impl-2.1-SNAPSHOT.jar:na]
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) [aspectjrt-1.6.12.jar:na]
at com.evolveum.midpoint.util.aspect.MidpointAspect.wrapSubsystem(MidpointAspect.java:176) [util-2.1-SNAPSHOT.jar:na]
at com.evolveum.midpoint.util.aspect.MidpointAspect.ajc$inlineAccessMethod$com_evolveum_midpoint_util_aspect_MidpointAspect$com_evolveum_midpoint_util_aspect_MidpointAspect$wrapSubsystem(MidpointAspect.java:1) [util-2.1-SNAPSHOT.jar:na]
at com.evolveum.midpoint.util.aspect.MidpointAspect.processResourceObjectChangeListenerNdc(MidpointAspect.java:81) [util-2.1-SNAPSHOT.jar:na]

...