org.infinispan.configuration.cache
Class LoadersConfiguration

java.lang.Object
  org.infinispan.configuration.cache.LoadersConfiguration

public class LoadersConfiguration
extends Object

Configuration for cache loaders and stores.

Method Summary

List<AbstractLoaderConfiguration>	cacheLoaders()
boolean	equals(Object o)
Boolean	fetchPersistentState() Loops through all individual cache loader configs and checks if fetchPersistentState is set on any of them
int	hashCode()
boolean	passivation() If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'.
boolean	preload() If true, when the cache starts, data stored in the cache store will be pre-loaded into memory.
boolean	shared() This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times.
String	toString()
boolean	usingAsyncStore()
boolean	usingCacheLoaders()
boolean	usingChainingCacheLoader()

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, wait, wait, wait

Method Detail

passivation

public boolean passivation()

If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. This gives you the ability to 'overflow' to disk, similar to swapping in an operating system.

If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.

preload

public boolean preload()

If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.

shared

public boolean shared()

This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store.

If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store. Note that this could be useful if each individual node has its own cache store - perhaps local on-disk.

cacheLoaders

public List<AbstractLoaderConfiguration> cacheLoaders()

fetchPersistentState

public Boolean fetchPersistentState()

Loops through all individual cache loader configs and checks if fetchPersistentState is set on any of them

usingCacheLoaders

public boolean usingCacheLoaders()

usingAsyncStore

public boolean usingAsyncStore()

usingChainingCacheLoader

public boolean usingChainingCacheLoader()

toString

public String toString()

Overrides:

toString in class Object

equals

public boolean equals(Object o)

Overrides:

equals in class Object

hashCode

public int hashCode()

Overrides:

hashCode in class Object