From 7e263d899f50ba2a9f5cdc888d76d7aa4481d698 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Thu, 15 Sep 2016 13:44:05 +0200 Subject: [PATCH] Polish cache doc Closes gh-6892 --- .../src/main/asciidoc/spring-boot-features.adoc | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index b63e28c4a64..958782a5f03 100644 --- a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -3762,7 +3762,8 @@ If you haven't defined a bean of type `CacheManager` or a `CacheResolver` named providers (in this order): * <> -* <> +* <> (EhCache 3, Hazelcast, + Infinspan, etc) * <> * <> * <> @@ -3810,12 +3811,16 @@ Generic caching is used if the context defines _at least_ one [[boot-features-caching-provider-jcache]] -==== JCache +==== JCache (JSR-107) JCache is bootstrapped via the presence of a `javax.cache.spi.CachingProvider` on the -classpath (i.e. a JSR-107 compliant caching library). It might happen that more than one -provider is present, in which case the provider must be explicitly specified. Even if the -JSR-107 standard does not enforce a standardized way to define the location of the -configuration file, Spring Boot does its best to accommodate with implementation details. +classpath (i.e. a JSR-107 compliant caching library). There are various compliant +libraries out there and Spring Boot provides dependency management for Ehcache 3, +Hazelcast and Infinispan). Any other compliant library can be added as well. + +It might happen that more than one provider is present, in which case the provider must +be explicitly specified. Even if the JSR-107 standard does not enforce a standardized +way to define the location of the configuration file, Spring Boot does its best to +accommodate with implementation details. [source,properties,indent=0] ----