Lutece Cache Implementation FAQs

Question 1

Can I prevent my cache from being cleared during a 'Reset All Caches' action?

Accepted Answer

Yes, by overriding the isPreventGlobalReset() method to return true. This is recommended for expensive configuration caches that shouldn't be cleared frequently.

Question 2

What is the preferred way to access a Lutece cache service?

Accepted Answer

The preferred method is using CDI @Inject for managed beans. For static contexts like Home classes, use CDI.current().select() instead of the deprecated getInstance() pattern.

Question 3

Where are Lutece cache settings managed?

Accepted Answer

Cache behavior can be tuned via the caches.properties file for defaults, while the enabled/disabled state is persisted in the Lutece datastore database.

Question 4

How does automatic cache invalidation work in this implementation?

Accepted Answer

It utilizes CDI events where the cache service observes ResourceEvent objects. When a specific resource type is modified, the service triggers a reset or removes specific keys.

Question 5

Why must I override the standard put/get methods in Lutece 8?

Accepted Answer

In Lutece 8, the base AbstractCacheableService does not perform null checks. If the cache is disabled in the datastore, these methods will throw a NullPointerException unless overridden with defensive guards.

Lutece Cache Implementation

Key Features

Use Cases

Lutece Cache Implementation

Key Features

Use Cases