org.hibernate.cache
Interface TransactionalDataRegion
- All Superinterfaces:
- Region
- All Known Subinterfaces:
- CollectionRegion, EntityRegion
- All Known Implementing Classes:
- BaseTransactionalDataRegion, BaseTransactionalDataRegionAdapter, ClusteredConcurrentTimestampsRegionImpl, CollectionRegionAdapter, CollectionRegionImpl, CollectionRegionImpl, EntityRegionAdapter, EntityRegionImpl, EntityRegionImpl, QueryResultsRegionImpl, QueryResultsRegionImpl, TimestampsRegionImpl, TransactionalDataRegionAdapter
public interface TransactionalDataRegion
- extends Region
Defines contract for regions which hold transactionally-managed data.
The data is not transactionally managed within the region; merely it is
transactionally-managed in relation to its association with a particular
Session
.
- Author:
- Steve Ebersole
Method Summary |
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. |
isTransactionAware
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.
getCacheDataDescription
CacheDataDescription getCacheDataDescription()
Copyright © 2001-2010 Red Hat, Inc. All Rights Reserved.