public interface TransactionalDataRegion extends Region
Defines contract for regions which hold transactionally-managed data.
<p/>
The data is not transactionally managed within the region; merely it is
transactionally-managed in relation to its association with a particular
Session
.
Modifier and Type | Method and Description |
---|---|
CacheDataDescription |
getCacheDataDescription()
Get the description of the type of data to be stored here, which would have been given to the RegionFactory
when creating this region
|
boolean |
isTransactionAware()
Is the underlying cache implementation aware of (and "participating in")
ongoing JTA transactions?
<p/>
Regions which report that they are transaction-aware are considered
"synchronous", in that we assume we can immediately (i.e.
|
contains, destroy, getElementCountInMemory, getElementCountOnDisk, getName, getSizeInMemory, getTimeout, nextTimestamp, toMap
boolean isTransactionAware()
Is the underlying cache implementation aware of (and "participating in") ongoing JTA transactions? <p/> 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).
CacheDataDescription getCacheDataDescription()
Get the description of the type of data to be stored here, which would have been given to the RegionFactory when creating this region
Copyright © 2001-2018 Red Hat, Inc. All Rights Reserved.