Issue 10686: (last) end_updates call on CacheListeners (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: 
Summary: Problem:
It is currently not clear that the modification states are cleared after the last call to the CacheListener (multiple cache listeners may be registered!). This should be clarified.

Solution:
Replace:
o Finally all the CacheListener::end_updates operations are triggered and the modification states of the updated objects is cleaned; the order in which these listeners are triggered is not specified.

With:
o Finally all the CacheListener::end_updates operations are triggered and the modification states of the updated objects is cleaned after the last CacheListener::end_updates has been triggered; the order in which these listeners are triggered is not specified.

Resolution: 
Revised Text: 
Actions taken:
February 12, 2007: received issue
Discussion: 
Clarify that after the (last) end_updates call on CacheListeners that all modification information is cleared. (section 3.1.6.4.1, last bullet)
End of Annotations:=====
s is issue # 10686	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


(last) end_updates call on CacheListeners

Problem:
It is currently not clear that the modification states are cleared after the last call to the CacheListener (multiple cache listeners may be registered!). This should be clarified.

Solution:
Replace:
o Finally all the CacheListener::end_updates operations are triggered and the modification states of the updated objects is cleaned; the order in which these listeners are triggered is not specified.

With:
o Finally all the CacheListener::end_updates operations are triggered and the modification states of the updated objects is cleaned after the last CacheListener::end_updates has been triggered; the order in which these listeners are triggered is not specified.