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 |
Package intended for simplifying the worked needed to implement
a caching provider. Centers around the concept of
StorageAccess
and
DomainDataStorageAccess
too implement most of the "grunt work" associated with the
implementation.
Most integrations would just:
implement a custom StorageAccess/DomainDataStorageAccess
implement a custom RegionFactoryTemplate, implementing specifically:
RegionFactoryTemplate#createDomainDataStorageAccess
RegionFactoryTemplate#createQueryResultsRegionStorageAccess
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 © 2001-2018 Red Hat, Inc. All Rights Reserved.