Issue 10745: cloned objects (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

What should happen to cloned objects that, when the CacheAccess is refreshed, are no longer covered by any contract? You cannot just treat them as if they were deleted. 

Solution:

Probably a special state needs to be introduced for this called NOT_COMPLIANT.

TBD.


Resolution: 
Revised Text: 
Actions taken:
February 14, 2007: received issue
Discussion: 
Indicate what should happen to cloned objects that, when the CacheAccess is refreshed, are no longer covered by any contract
End of Annotations:=====
s is issue # 10745	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


cloned objects
Indicate what should happen to cloned objects that, when the CacheAccess is refreshed, are no longer covered by any contract

Problem:

What should happen to cloned objects that, when the CacheAccess is refreshed, are no longer covered by any contract? You cannot just treat them as if they were deleted. 

Solution:

Probably a special state needs to be introduced for this called NOT_COMPLIANT.

TBD.