Invalidating or Destroying Cached Entries
- Through direct API calls from the client.
- Through expiration activities based on the entry’s statistics and the region’s attribute settings.
Note: A user-defined cache writer is called before an operation is completed, and can abort an entry destroy operation.
Whether carried out explicitly or through expiration activities, invalidation and destruction cause event notification: The
CacheEvent object has an
isExpiration flag that is set to true for events resulting from expiration activities, and set to
false for all other events.