public abstract class BaseTransactionalDataRegion extends BaseRegion implements TransactionalDataRegion
TransactionalDataRegion
implementors.address, cacheAdapter, invalidateState, invalidationMutex, replication, transactionManager
Constructor and Description |
---|
BaseTransactionalDataRegion(CacheAdapter cacheAdapter,
String name,
CacheDataDescription metadata,
TransactionManager transactionManager,
RegionFactory factory) |
Modifier and Type | Method and Description |
---|---|
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.
|
checkValid, contains, destroy, get, getAddress, getCacheAdapter, getElementCountInMemory, getElementCountOnDisk, getName, getOwnerForPut, getSizeInMemory, getTimeout, getTransactionManager, invalidateRegion, isValid, nextTimestamp, resume, suspend, toMap
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
contains, destroy, getElementCountInMemory, getElementCountOnDisk, getName, getSizeInMemory, getTimeout, nextTimestamp, toMap
public BaseTransactionalDataRegion(CacheAdapter cacheAdapter, String name, CacheDataDescription metadata, TransactionManager transactionManager, RegionFactory factory)
public CacheDataDescription getCacheDataDescription()
getCacheDataDescription
in interface TransactionalDataRegion
public boolean isTransactionAware()
TransactionalDataRegion
isTransactionAware
in interface TransactionalDataRegion
Copyright © 2012 JBoss by Red Hat. All Rights Reserved.