Spring/spring-session-data-geode
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Replace all references to Pivotal GemFire with VMware Tanzu GemFire.

Browse Source
This commit is contained in:
John Blum
2021-06-10 10:27:57 -07:00
parent 1c25955c0a
commit a204cad791
6 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/docs/asciidoc/guides/boot-gemfire-with-scoped-proxies.adoc
View File

@@ -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...

4
docs/src/docs/asciidoc/guides/xml-gemfire-clientserver.adoc
View File

@@ -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.

2
docs/src/docs/asciidoc/guides/xml-gemfire-p2p.adoc
View File

@@ -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.