public class ReadOnlyStore extends AbstractDelegatingStore
CacheLoader
, i.e., suppressing all write
methods.Constructor and Description |
---|
ReadOnlyStore(CacheStore delegate) |
Modifier and Type | Method and Description |
---|---|
void |
clear()
Clears all entries in the store
|
void |
commit(GlobalTransaction tx)
Commits a transaction that has been previously prepared.
|
void |
fromStream(ObjectInput inputStream)
Writes contents of the stream to the store.
|
void |
prepare(List<? extends Modification> list,
GlobalTransaction tx,
boolean isOnePhase)
Issues a prepare call with a set of modifications to be applied to the cache store
|
void |
purgeExpired()
Purges expired entries from the store.
|
boolean |
remove(Object key)
Removes an entry in the store.
|
void |
rollback(GlobalTransaction tx)
Rolls back a transaction that has been previously prepared
This method may be invoked on a transaction for which there is no prior
CacheStore.prepare(java.util.List, org.infinispan.transaction.xa.GlobalTransaction, boolean) . |
void |
store(InternalCacheEntry ed)
Stores an entry
|
containsKey, getCacheStoreConfig, getConfigurationClass, getDelegate, init, load, load, loadAll, loadAllKeys, removeAll, setDelegate, start, stop, toStream
public ReadOnlyStore(CacheStore delegate)
public void store(InternalCacheEntry ed)
CacheStore
store
in interface CacheStore
store
in class AbstractDelegatingStore
ed
- entry to storepublic void fromStream(ObjectInput inputStream)
CacheStore
CacheStore.toStream(java.io.ObjectOutput)
. While not a
requirement, it is recommended that implementations make use of the StreamingMarshaller
when dealing with the stream to make use of efficient marshalling.
It is imperative that implementations do not close the stream after finishing with it.
It is also recommended that implementations use their own start and end markers on the stream since
other processes may write additional data to the stream after the cache store has written to it. As such, either
markers or some other mechanism to prevent the store from reading too much information should be employed when
writing to the stream in CacheStore.fromStream(java.io.ObjectInput)
to prevent data corruption.
It can be assumed that the stream passed in already performs buffering such that the cache store implementation
doesn't have to.
fromStream
in interface CacheStore
fromStream
in class AbstractDelegatingStore
inputStream
- stream to read frompublic void clear()
CacheStore
clear
in interface CacheStore
clear
in class AbstractDelegatingStore
public boolean remove(Object key)
CacheStore
remove
in interface CacheStore
remove
in class AbstractDelegatingStore
key
- key to removepublic void purgeExpired()
CacheStore
purgeExpired
in interface CacheStore
purgeExpired
in class AbstractDelegatingStore
public void commit(GlobalTransaction tx)
CacheStore
CacheStore.prepare(java.util.List, org.infinispan.transaction.xa.GlobalTransaction, boolean)
. The implementation would
need to deal with this case accordingly. Typically, this would be a no-op, after ensuring any resources attached
to the transaction are cleared up.
Also note that this method may be invoked on a thread which is different from the CacheStore.prepare(java.util.List, org.infinispan.transaction.xa.GlobalTransaction, boolean)
invocation. As such, ThreadLocal
s should not be relied upon to maintain transaction context.
commit
in interface CacheStore
commit
in class AbstractDelegatingStore
tx
- tx to commitpublic void rollback(GlobalTransaction tx)
CacheStore
CacheStore.prepare(java.util.List, org.infinispan.transaction.xa.GlobalTransaction, boolean)
. The implementation would
need to deal with this case accordingly. Typically, this would be a no-op, after ensuring any resources attached
to the transaction are cleared up.
Also note that this method may be invoked on a thread which is different from the CacheStore.prepare(java.util.List, org.infinispan.transaction.xa.GlobalTransaction, boolean)
invocation. As such, ThreadLocal
s should not be relied upon to maintain transaction context.
rollback
in interface CacheStore
rollback
in class AbstractDelegatingStore
tx
- tx to roll backpublic void prepare(List<? extends Modification> list, GlobalTransaction tx, boolean isOnePhase)
CacheStore
prepare
in interface CacheStore
prepare
in class AbstractDelegatingStore
list
- modifications to be appliedtx
- transaction identifierisOnePhase
- if true, there will not be a commit or rollback phase and changes should be flushed
immediatelyCopyright © 2012 JBoss by Red Hat. All Rights Reserved.