public abstract class BaseTransactionalDataRegionAdapter extends BaseRegionAdapter implements TransactionalDataRegion
Modifier and Type | Field and Description |
---|---|
protected CacheDataDescription |
metadata |
settings, underlyingCache
Modifier | Constructor and Description |
---|---|
protected |
BaseTransactionalDataRegionAdapter(Cache underlyingCache,
Settings settings,
CacheDataDescription metadata) |
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.
|
clear, contains, destroy, getElementCountInMemory, getElementCountOnDisk, getName, getSizeInMemory, getTimeout, nextTimestamp, toMap
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
contains, destroy, getElementCountInMemory, getElementCountOnDisk, getName, getSizeInMemory, getTimeout, nextTimestamp, toMap
protected final CacheDataDescription metadata
protected BaseTransactionalDataRegionAdapter(Cache underlyingCache, Settings settings, CacheDataDescription metadata)
public boolean isTransactionAware()
TransactionalDataRegion
isTransactionAware
in interface TransactionalDataRegion
public CacheDataDescription getCacheDataDescription()
getCacheDataDescription
in interface TransactionalDataRegion
Copyright © 2002-2017 Red Hat Middleware, LLC. All Rights Reserved