StoreConfiguration (Infinispan JavaDoc All 9.0.3.Final API)

All Known Implementing Classes:

AbstractJdbcStoreConfiguration, AbstractStoreConfiguration, ClusterLoaderConfiguration, CustomStoreConfiguration, JdbcStringBasedStoreConfiguration, JpaStoreConfiguration, RemoteStoreConfiguration, RestStoreConfiguration, SingleFileStoreConfiguration
```
public interface StoreConfiguration
```
StoreConfiguration contains generic configuration elements available to all the stores.

Since:

5.2

Author:

Tristan Tarrant, Mircea Markus

Method Summary

All Methods Instance Methods Abstract Methods Deprecated Methods
Modifier and Type	Method and Description
`AsyncStoreConfiguration`	`async()` Configuration for the async cache loader.
`boolean`	`fetchPersistentState()` If true, fetch persistent state when joining a cluster.
`boolean`	`ignoreModifications()` If true, any operation that modifies the cache (put, remove, clear, store...etc) won't be applied to the cache store.
`boolean`	`preload()`
`Properties`	`properties()`
`boolean`	`purgeOnStartup()` If true, purges this cache store when it starts up.
`boolean`	`shared()`
`SingletonStoreConfiguration`	`singletonStore()` Deprecated. Singleton writers will be removed in 10.0. If it is desirable that all nodes don't write to the underlying store then a shared store should be used instead, as this only performs store writes at a key's primary owner.
`boolean`	`transactional()`

- Method Detail
  - async
```
AsyncStoreConfiguration async()
```
    Configuration for the async cache loader. If enabled, this provides you with asynchronous writes to the cache store, giving you 'write-behind' caching.
  - singletonStore
```
@Deprecated
SingletonStoreConfiguration singletonStore()
```
    Deprecated. Singleton writers will be removed in 10.0. If it is desirable that all nodes don't write to the underlying store then a shared store should be used instead, as this only performs store writes at a key's primary owner.
    
    SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store. The coordinator of the cluster will be responsible for the underlying CacheStore. SingletonStore is a simply facade to a real CacheStore implementation. It always delegates reads to the real CacheStore.
  - purgeOnStartup
```
boolean purgeOnStartup()
```
    If true, purges this cache store when it starts up.
  - fetchPersistentState
```
boolean fetchPersistentState()
```
    If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled. Persistent state transfer with a shared cache store does not make sense, as the same persistent store that provides the data will just end up receiving it. Therefore, if a shared cache store is used, the cache will not allow a persistent state transfer even if a cache store has this property set to true. Finally, setting it to true only makes sense if in a clustered environment, and only 'replication' and 'invalidation' cluster modes are supported.
  - ignoreModifications
```
boolean ignoreModifications()
```
    If true, any operation that modifies the cache (put, remove, clear, store...etc) won't be applied to the cache store. This means that the cache store could become out of sync with the cache.
  - preload
```
boolean preload()
```
  - shared
```
boolean shared()
```
  - transactional
```
boolean transactional()
```
  - properties
```
Properties properties()
```

Interface StoreConfiguration

Method Summary

Method Detail

async

singletonStore

purgeOnStartup

fetchPersistentState

ignoreModifications

preload

shared

transactional

properties