Issue 10673: Clarify exceptions for enable_updates and disable_updates operations of Cac (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: 
Summary: Problem:
In section 3.1.6.3.4 on page 3-23 for the descriptions of the enable and disable updates operation it should state a PreconditionNotMet is thrown if the cache is created with a usage of WRITE_ONLY. It should also state that multiple calls to the operations is considered a no-op. It should also be stated that calling the disable_updates operation results in all cache listeners being triggered with the on_updates_disabled call and for the enable the on_updates_enabled is called in scope of the thread making the call to enable or disable updates. 

Solution:

Replace (see issue XXX(PT-DLRL-TYPO-0011) which already made changes to the disable_updates description):
o disable_updates causes incoming but not yet applied updates to be registered for further application, any update round in progress will be completed before the disable updates instruction is taken into account.

o enable_updates causes the registered (and thus not applied) updates to be takeninto account, and thus to trigger the attached Listener, if any.

With:
o disable_updates causes incoming but not yet applied updates to be registered for further application, any update round in progress will be completed before the disable updates instruction is taken into account. All registered CacheListeners will be triggered with the on_updates_disabled call (in scope of the thread calling the disable_updates operation) signaling, to any interested party, that updates on the Cache will no longer be automatically processed and no longer result in listener triggers. If the cache_usage of the Cache is WRITE_ONLY then a PreconditionNotMet is raised. 

o enable_updates causes the registered (and thus not applied) updates to be taken into account, and thus to trigger the attached CacheListeners, if any. All registered CacheListeners will be triggered before any updates are applied with the on_updates_enabled call (in scope of the thread calling the enabled_updates operation) signaling, to any interested party, that the updates on the Cache will be automatically processed and thus result in listener triggers. If the cache_usage of the Cache is WRITE_ONLY then a PreconditionNotMet is raised.


In the IDL description in section 3.2.1.2 on page 3-58 replace:
// --- Updates management
void enable_updates ();
void disable_updates ();
With:
// --- Updates management
void enable_updates () raises (PreconditionNotMet);
void disable_updates ()raises (PreconditionNotMet);;
Resolution: 
Revised Text: 
Actions taken:
February 12, 2007: received issue
Discussion: 
Clarify exceptions for the enable_updates and disable_updates operations of the Cache. Also clarify that the cache listener should be triggered within the scope of these operations
End of Annotations:=====
s is issue # 10673

Clarify exceptions for enable_updates and disable_updates operations of Cache
Clarify exceptions for the enable_updates and disable_updates operations of the Cache. Also clarify that the cache listener should be triggered within the scope of these operations

Problem:
In section 3.1.6.3.4 on page 3-23 for the descriptions of the enable and disable updates operation it should state a PreconditionNotMet is thrown if the cache is created with a usage of WRITE_ONLY. It should also state that multiple calls to the operations is considered a no-op. It should also be stated that calling the disable_updates operation results in all cache listeners being triggered with the on_updates_disabled call and for the enable the on_updates_enabled is called in scope of the thread making the call to enable or disable updates. 

Solution:

Replace (see issue XXX(PT-DLRL-TYPO-0011) which already made changes to the disable_updates description):
o disable_updates causes incoming but not yet applied updates to be registered for further application, any update round in progress will be completed before the disable updates instruction is taken into account.

o enable_updates causes the registered (and thus not applied) updates to be takeninto account, and thus to trigger the attached Listener, if any.

With:
o disable_updates causes incoming but not yet applied updates to be registered for further application, any update round in progress will be completed before the disable updates instruction is taken into account. All registered CacheListeners will be triggered with the on_updates_disabled call (in scope of the thread calling the disable_updates operation) signaling, to any interested party, that updates on the Cache will no longer be automatically processed and no longer result in listener triggers. If the cache_usage of the Cache is WRITE_ONLY then a PreconditionNotMet is raised. 

o enable_updates causes the registered (and thus not applied) updates to be taken into account, and thus to trigger the attached CacheListeners, if any. All registered CacheListeners will be triggered before any updates are applied with the on_updates_enabled call (in scope of the thread calling the enabled_updates operation) signaling, to any interested party, that the updates on the Cache will be automatically processed and thus result in listener triggers. If the cache_usage of the Cache is WRITE_ONLY then a PreconditionNotMet is raised.


In the IDL description in section 3.2.1.2 on page 3-58 replace:
// --- Updates management
void enable_updates ();
void disable_updates ();
With:
// --- Updates management
void enable_updates () raises (PreconditionNotMet);
void disable_updates ()raises (PreconditionNotMet);;