CollectionRegion

Class Overview

Defines the contract for a cache region which will specifically be used to store collection data.

Impl note: Hibernate always deals with changes to collections which (potentially) has its data in the L2 cache by removing that collection data; in other words it never tries to update the cached state, thereby allowing it to avoid a bunch of concurrency problems.

Summary

[Expand] Inherited Methods
From interface org.hibernate.cache.Region abstract boolean contains(Object key) Determine whether this region contains data for the given key. abstract void destroy() The "end state" contract of the region's lifecycle. abstract long getElementCountInMemory() The count of entries currently contained in the regions in-memory store. abstract long getElementCountOnDisk() The count of entries currently contained in the regions disk store. abstract String getName() Retrieve the name of this region. abstract long getSizeInMemory() The number of bytes is this cache region currently consuming in memory. abstract int getTimeout() abstract long nextTimestamp() abstract Map toMap() Get the contents of this region as a map.
From interface org.hibernate.cache.TransactionalDataRegion abstract CacheDataDescription getCacheDataDescription() abstract boolean isTransactionAware() Is the underlying cache implementation aware of (and "participating in") ongoing JTA transactions? Regions which report that they are transaction-aware are considered "synchronous", in that we assume we can immediately (i.e.