Replace all references to Pivotal GemFire with VMware Tanzu GemFire.
This commit is contained in:
@@ -25,7 +25,7 @@ to process client HTTP requests.
|
||||
This sample is based on a https://stackoverflow.com/questions/45674137/can-session-scope-beans-be-used-with-spring-session-and-gemfire[_StackOverflow_ post],
|
||||
which posed the following question...
|
||||
|
||||
> _Can session scope beans be used with Spring Session and Pivotal GemFire?_
|
||||
> _Can session scope beans be used with Spring Session and VMware Tanzu GemFire?_
|
||||
|
||||
The poster of the question when on to state and ask...
|
||||
|
||||
@@ -70,7 +70,7 @@ If you are using _Maven_, include the following `dependencies` in your `pom.xml`
|
||||
</dependencies>
|
||||
----
|
||||
|
||||
NOTE: If you are using Pivotal GemFire instead of Apache Geode, you may substitute the `spring-session-data-gemfire`
|
||||
NOTE: If you are using VMware Tanzu GemFire instead of Apache Geode, you may substitute the `spring-session-data-gemfire`
|
||||
artifact for `spring-session-data-geode`.
|
||||
|
||||
ifeval::["{version-snapshot}" == "true"]
|
||||
@@ -174,7 +174,7 @@ in the Apache Geode User Guide.
|
||||
|
||||
NOTE: For more information on configuring _Spring Data for Apache Geode_, refer to the {sdg-docs}[Reference Guide].
|
||||
|
||||
==== Enabling Pivotal GemFire HttpSession Management
|
||||
==== Enabling VMware Tanzu GemFire HttpSession Management
|
||||
|
||||
The `@EnableGemFireHttpSession` annotation enables developers to configure certain aspects of both Spring Session
|
||||
and Apache Geode out-of-the-box using the following attributes:
|
||||
|
||||
@@ -102,7 +102,7 @@ include::{samples-dir}xml/gemfire-clientserver/src/main/webapp/WEB-INF/spring/se
|
||||
----
|
||||
|
||||
<1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode `ClientCache`
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
|
||||
setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
|
||||
if unspecified.
|
||||
<2> We must create an instance of an Apache Geode `ClientCache`. We initialize it with our `gemfireProperties`.
|
||||
@@ -134,7 +134,7 @@ include::{samples-dir}xml/gemfire-clientserver/src/main/resources/META-INF/sprin
|
||||
----
|
||||
|
||||
<1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode peer `Cache`
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
|
||||
setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
|
||||
if unspecified.
|
||||
<2> We must configure an Apache Geode peer `Cache` instance. We initialize it with the Apache Geode properties.
|
||||
|
||||
@@ -103,7 +103,7 @@ include::{samples-dir}xml/gemfire-p2p/src/main/webapp/WEB-INF/spring/session.xml
|
||||
----
|
||||
|
||||
<1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode peer `Cache`
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
|
||||
using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
|
||||
setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
|
||||
if unspecified.
|
||||
<2> We must configure an Apache Geode peer `Cache` instance. We initialize it with the Apache Geode properties.
|
||||
|
||||
Reference in New Issue
Block a user