Issue 10679: Clarify usage of the destroy() operation on the ObjectRoot (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: 
Summary: Problem:

It should be clarified that a destroyed ObjectRoot is only removed from the CacheAccess after the write() operation has been performed. The ObjectRoot will produce AlreadyDeleted exceptions only after that time.

Solution:
Replace:
o mark the object for destruction (destroy), to be executed during a write operation. If the object is not located in a writeable CacheAccess, a PreconditionNotMet is raised.
With:
o mark the object for destruction (destroy), to be executed during a write operation on the owning CacheAccess. After the write operation has been completed the object will be removed from the CacheAccess and subsequent calls to operations on the object may result in AlreadyDeleted exceptions being raised.  If the object is not located in a writeable CacheAccess, a PreconditionNotMet is raised.

Resolution: 
Revised Text: 
Actions taken:
February 12, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 10679	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


Clarify usage of the destroy() operation on the ObjectRoot

Problem:

It should be clarified that a destroyed ObjectRoot is only removed from the CacheAccess after the write() operation has been performed. The ObjectRoot will produce AlreadyDeleted exceptions only after that time.

Solution:
Replace:
o mark the object for destruction (destroy), to be executed during a write operation. If the object is not located in a writeable CacheAccess, a PreconditionNotMet is raised.
With:
o mark the object for destruction (destroy), to be executed during a write operation on the owning CacheAccess. After the write operation has been completed the object will be removed from the CacheAccess and subsequent calls to operations on the object may result in AlreadyDeleted exceptions being raised.  If the object is not located in a writeable CacheAccess, a PreconditionNotMet is raised.