mirror of
https://github.com/spring-projects/spring-petclinic.git
synced 2025-07-15 12:15:50 +00:00
Merge pull request #335 from cruftex:fix-cache-comment
* pr/335: Polish "Clarify cache configuration" Clarify cache configuration
This commit is contained in:
commit
5f7574570e
1 changed files with 13 additions and 4 deletions
|
@ -1,12 +1,16 @@
|
|||
package org.springframework.samples.petclinic.system;
|
||||
|
||||
import javax.cache.configuration.MutableConfiguration;
|
||||
|
||||
import org.springframework.boot.autoconfigure.cache.JCacheManagerCustomizer;
|
||||
import org.springframework.cache.annotation.EnableCaching;
|
||||
import org.springframework.context.annotation.Bean;
|
||||
import org.springframework.context.annotation.Configuration;
|
||||
|
||||
import javax.cache.configuration.MutableConfiguration;
|
||||
|
||||
/**
|
||||
* Cache configuration intended for caches providing the JCache API. This configuration creates the used cache for the
|
||||
* application and enables statistics that become accessible via JMX.
|
||||
*/
|
||||
@Configuration
|
||||
@EnableCaching
|
||||
class CacheConfiguration {
|
||||
|
@ -18,9 +22,14 @@ class CacheConfiguration {
|
|||
};
|
||||
}
|
||||
|
||||
/**
|
||||
* Create a simple configuration that enable statistics via the JCache programmatic configuration API.
|
||||
* <p>
|
||||
* Within the configuration object that is provided by the JCache API standard, there is only a very limited set of
|
||||
* configuration options. The really relevant configuration options (like the size limit) must be set via a
|
||||
* configuration mechanism that is provided by the selected JCache implementation.
|
||||
*/
|
||||
private javax.cache.configuration.Configuration<Object, Object> cacheConfiguration() {
|
||||
// Create a cache using infinite heap. A real application will want to use a more fine-grained configuration,
|
||||
// possibly using an implementation-dependent API
|
||||
return new MutableConfiguration<>().setStatisticsEnabled(true);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue