Page History
...
When putting objects to the cache you can restrict their lifetime. In this case, instead of checking the validity of cached objects, you can simply let them expire over time.
Rebuild the cache on non-persistent implementations after server restart
| Warning |
|---|
Whether cache is persistent depends on the underlying implementation. For non-persistent implementations the cache must be rebuilt after server restart. See Cache implementations for more. |
Implementations:
| Not persistent | EhCache with free license |
| Persistent |
Get the cache
Achieve an instance of
| Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
...
| Advanced Tables - Table Plus | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||
|
The /modules/cache/config/cacheFactory/caches/fooBarCache node defines the cache name. fooBarCache is the "name" of the cache which was also used above when acquiring the Cache object within Java code.
...
Overview
Content Tools