org.hibernate.cache.spi.support.StorageAccess and
org.hibernate.cache.spi.support.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
org.hibernate.boot.registry.selector.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.
| Modifier and Type | Interface and Description |
|---|---|
| public interface | DomainDataStorageAccess
Specialization of StorageAccess for domain data regions |
| public interface | StorageAccess
A general read/write abstraction over the specific "cache" object from the caching provider. |
| Modifier and Type | Enum and Description |
|---|---|
| public enum |