public abstract class

BaseTransactionalDataRegionAdapter

extends BaseRegionAdapter
implements TransactionalDataRegion

java.lang.Object
↳	org.hibernate.cache.impl.bridge.BaseRegionAdapter
	↳	org.hibernate.cache.impl.bridge.BaseTransactionalDataRegionAdapter

Known Direct Subclasses

CollectionRegionAdapter, EntityRegionAdapter

Class Overview

Summary

Fields
protected final CacheDataDescription	metadata

[Expand]

Inherited Fields

From class org.hibernate.cache.impl.bridge.BaseRegionAdapter

Protected Constructors
	BaseTransactionalDataRegionAdapter(Cache underlyingCache, Settings settings, CacheDataDescription metadata)

Public Methods
CacheDataDescription	getCacheDataDescription()
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.

[Expand]

Inherited Methods

From class org.hibernate.cache.impl.bridge.BaseRegionAdapter

void	clear()
boolean	contains(Object key) Determine whether this region contains data for the given key.
void	destroy() The "end state" contract of the region's lifecycle.
long	getElementCountInMemory() The count of entries currently contained in the regions in-memory store.
long	getElementCountOnDisk() The count of entries currently contained in the regions disk store.
String	getName() Retrieve the name of this region.
long	getSizeInMemory() The number of bytes is this cache region currently consuming in memory.
int	getTimeout()
long	nextTimestamp()
Map	toMap() Get the contents of this region as a map.

From class java.lang.Object

From interface org.hibernate.cache.Region

From interface org.hibernate.cache.TransactionalDataRegion

Fields

protected final CacheDataDescription metadata

Protected Constructors

protected BaseTransactionalDataRegionAdapter (Cache underlyingCache, Settings settings, CacheDataDescription metadata)

Public Methods

public CacheDataDescription getCacheDataDescription ()

public 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. synchronously) write the changes to the cache and that the cache will properly manage application of the written changes within the bounds of ongoing JTA transactions. Conversely, regions reporting false are considered "asynchronous", where it is assumed that changes must be manually delayed by Hibernate until we are certain that the current transaction is successful (i.e. maintaining READ_COMMITTED isolation).

Returns

True if transaction aware; false otherwise.

Classes