Description Holger Schill 2011-03-07 10:08:59 EST

Since 2.0.0 a link to an element is valid even when the link is not unique.

In 1.0.2 a link is broken in this case because a link must be unique.

Because of that there is a problem in DefaultResourceDescriptionManager while calculation of affected resource. 

To figure out if a resource is affected at first the outgoingReferences are analyzed. In the case that a link is broken, because it is not unique, there is no ReferenceDescription for that. 
Next all visible Container are asked if from the view of a candidate a container contains the deleted resource. The state of the index does not contain a deleted resource anymore because during update all deleted resources are removed. Because of that a resource with a broken not unique link will never be affected.

This special case is also relevant for 2.0.0, because if the visible containers are asked to figure out if a deleted resource is visible to a candidate the candidate will never be affected.