From 4b906e426a02eeb3fd78190aeee0491f01ba5f3a Mon Sep 17 00:00:00 2001 From: John Blum Date: Wed, 29 Aug 2018 16:01:08 -0700 Subject: [PATCH] Add note about Spring Boot not recognizing or respecting 'spring.session.store-type' set to 'gemfire' or 'geode'. --- spring-geode-docs/src/docs/asciidoc/session.adoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/spring-geode-docs/src/docs/asciidoc/session.adoc b/spring-geode-docs/src/docs/asciidoc/session.adoc index 6e16d32a..cebbde16 100644 --- a/spring-geode-docs/src/docs/asciidoc/session.adoc +++ b/spring-geode-docs/src/docs/asciidoc/session.adoc @@ -1,4 +1,4 @@ -[[geode-session] +[[geode-session]] == Spring Session This section covers auto-configuration of Spring Session using either Apache Geode or Pivotal GemFire to manage @@ -157,3 +157,7 @@ Again, see Spring Boot {spring-boot-docs-html}/boot-features-session.html[docs] TIP: It is possible to include multiple providers on the classpath of your Spring Boot application. For instance, you might be using Redis to cache your application's (HTTP) Session state while using either Apache Geode or Pivotal GemFire as your application's persistent store (_System of Record_). + +NOTE: Spring Boot does not properly or correctly recognize `spring.session.store-type=[gemfire|geode]` even though +Spring Boot for Apache Geode/Pivotal GemFire is setup to handle either of these property values +(i.e. either "`gemfire`" or "`geode`").