Base contract for accessing the underlying cached data for a particular Navigable of the user's domain model in a transactionally ACID manner.
Contract for managing transactional and concurrent access to cached collection data.
Contract for managing transactional and concurrent access to cached entity data.
Contract for managing transactional and concurrent access to cached naturalId data.
Memento object for use by synchronous concurrency strategies
The types of access strategies available.
Indicates that an unknown AccessType external name was encountered or that an AccessType was requested that the underlying cache provider does not support.
Defines contracts for transactional and concurrent access to cached
collection data. Transactions pass in a
timestamp indicating transaction start time which is then used to protect against concurrent access (exactly how
that occurs is based on the actual access-strategy impl used). Two different implementation patterns are provided
nonstrict-read-write. The only synchronous access strategy is
Note that, for an asynchronous cache, cache invalidation must be a two step process (lock->unlock or
lock->afterUpdate), since this is the only way to guarantee consistency with the database for a nontransactional
cache implementation. For a synchronous cache, cache invalidation is a single step process (evict or update).
Hence, these contracts (
org.hibernate.cache.spi.access.CollectionRegionAccessStrategy) define a three step process to cater for both
models (see the individual contracts for details).
Note that query result caching does not go through an access strategy; those caches are managed directly against
Copyright © 2019 JBoss by Red Hat. All rights reserved.