Implementors should define a constructor in one of two forms:
java.util.Properties )start being called. For an example, have a look at
org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge
where we need the properties in order to determine which legacy
CacheProvider to use so that we can answer the
isMinimalPutsEnabledByDefault() question for the
org.hibernate.cfg.SettingsFactory .
| Modifier and Type | Method and Description |
|---|---|
| public CollectionRegion | Returns: The built regionThe name of the region. regionName, Properties Configuration properties. properties, CacheDataDescription Information regarding the type of data to be cached metadata)Build a cache region specialized for storing collection data. |
| public EntityRegion | Returns: The built regionThe name of the region. regionName, Properties Configuration properties. properties, CacheDataDescription Information regarding the type of data to be cached metadata)Build a cache region specialized for storing entity data. |
| public QueryResultsRegion | Returns: The built regionThe name of the region. regionName, Properties Configuration properties. properties)Build a cache region specialized for storing query results |
| public TimestampsRegion | Returns: The built regionThe name of the region. regionName, Properties Configuration properties. properties)Build a cache region specialized for storing update-timestamps data. |
| public AccessType | Returns: This factory's default access type.Get the default access type for |
| public boolean | Returns: True if "minimal puts" should be performed by default; false otherwise.By default should we perform "minimal puts" when using this second level cache implementation? |
| public long | |
| public void | start(Settings
The settings in effect. settings, Properties The defined cfg properties properties)Lifecycle callback to perform any necessary initialization of the underlying cache implementation(s). |
| public void | stop()
Lifecycle callback to perform any necessary cleanup of the underlying cache implementation(s). |
| buildCollectionRegion | back to summary |
|---|---|
| public CollectionRegion buildCollectionRegion(String regionName, Properties properties, CacheDataDescription metadata) throws CacheException Build a cache region specialized for storing collection data.
| |
| buildEntityRegion | back to summary |
|---|---|
| public EntityRegion buildEntityRegion(String regionName, Properties properties, CacheDataDescription metadata) throws CacheException Build a cache region specialized for storing entity data.
| |
| buildQueryResultsRegion | back to summary |
|---|---|
| public QueryResultsRegion buildQueryResultsRegion(String regionName, Properties properties) throws CacheException Build a cache region specialized for storing query results
| |
| buildTimestampsRegion | back to summary |
|---|---|
| public TimestampsRegion buildTimestampsRegion(String regionName, Properties properties) throws CacheException Build a cache region specialized for storing update-timestamps data.
| |
| getDefaultAccessType | back to summary |
|---|---|
| public AccessType getDefaultAccessType() Get the default access type for
| |
| isMinimalPutsEnabledByDefault | back to summary |
|---|---|
| public boolean isMinimalPutsEnabledByDefault() By default should we perform "minimal puts" when using this second level cache implementation?
| |
| nextTimestamp | back to summary |
|---|---|
| public long nextTimestamp() Generate a timestamp. This is generally used for cache content locking/unlocking purposes depending upon the access-strategy being used.
| |
| start | back to summary |
|---|---|
| public void start(Settings settings, Properties properties) throws CacheException Lifecycle callback to perform any necessary initialization of the
underlying cache implementation(s). Called exactly once during the
construction of a
| |
| stop | back to summary |
|---|---|
| public void stop() Lifecycle callback to perform any necessary cleanup of the underlying
cache implementation(s). Called exactly once during
| |