See: Description
Interface | Description |
---|---|
AbstractDomainDataRegion.Destructible |
Optional interface caching implementors can implement in their
CachedDomainDataAccess impls to automatically have them destroyed
when this region is destroyed
|
AbstractReadWriteAccess.Lockable |
Interface type implemented by all wrapper objects in the cache.
|
DomainDataStorageAccess |
Specialization of StorageAccess for domain data regions
|
StorageAccess |
A general read/write abstraction over the specific "cache"
object from the caching provider.
|
Enum | Description |
---|---|
AccessedDataClassification |
StorageAccess
and
DomainDataStorageAccess
too implement most of the "grunt work" associated with the
implementation.
Most integrations would just:
1. implement a custom StorageAccess/DomainDataStorageAccess
2. implement a custom RegionFactoryTemplate, implementing specifically:
a. `RegionFactoryTemplate#createDomainDataStorageAccess`
b. `RegionFactoryTemplate#createQueryResultsRegionStorageAccess`
c. `RegionFactoryTemplate#createTimestampsRegionStorageAccess`
Voila.. functioning cache provider
The preferred approach to "provide a integration" is through a custom
StrategyRegistrationProvider
Both `hibernate-testing` (`org.hibernate.testing.cache.CachingRegionFactory`)
and `hibernate-jcache` (`org.hibernate.cache.jcache.internal.JCacheRegionFactory`)
provide examples of using this support package to implement a caching
provider.Copyright © 2021 JBoss by Red Hat. All rights reserved.