From d271a4ad1d06f46783ba491d56c5c74f9bc3986e Mon Sep 17 00:00:00 2001 From: Vedran Pavic Date: Mon, 29 Jan 2018 18:12:01 +0100 Subject: [PATCH] Polish contribution Closes gh-920 --- .../docs/asciidoc/guides/httpsession-gemfire-boot.adoc | 6 +++--- .../guides/httpsession-gemfire-clientserver-xml.adoc | 4 ++-- .../guides/httpsession-gemfire-clientserver.adoc | 10 +++++----- .../asciidoc/guides/httpsession-gemfire-p2p-xml.adoc | 2 +- .../docs/asciidoc/guides/httpsession-gemfire-p2p.adoc | 4 ++-- docs/src/docs/asciidoc/index.adoc | 2 +- 6 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/src/docs/asciidoc/guides/httpsession-gemfire-boot.adoc b/docs/src/docs/asciidoc/guides/httpsession-gemfire-boot.adoc index 73a98ef4..a4e4720c 100644 --- a/docs/src/docs/asciidoc/guides/httpsession-gemfire-boot.adoc +++ b/docs/src/docs/asciidoc/guides/httpsession-gemfire-boot.adoc @@ -95,7 +95,7 @@ and managed by GemFire. As well, we have specified an arbitrary expiration attr for when the Session will timeout, which is triggered by a GemFire Region entry expiration event that also invalidates the Session object in the Region. <2> Next, we define a few `Properties` that allow us to configure certain aspects of the GemFire Server using -http://gemfire.docs.pivotal.io/docs-gemfire/reference/topics/gemfire_properties.html[GemFire's System properties]. +http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/gemfire_properties.html[GemFire's System properties]. <3> Then, we create an instance of the GemFire `Cache` using our defined `Properties`. <4> Finally, we configure and start a `CacheServer` running in the GemFire Server to listen for connections from cache clients. The `CacheServer's` `Socket` will be used to connect our GemFire cache client, @@ -159,7 +159,7 @@ and GemFire out-of-the-box using the following attributes: * `maxInactiveIntervalInSeconds` - controls _HttpSession_ idle-timeout expiration (defaults to **30 minutes**). * `regionName` - specifies the name of the GemFire Region used to store `HttpSession` state (defaults is "*ClusteredSpringSessions*"). * `clientRegionShort` - specifies GemFire's http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/management_all_region_types/chapter_overview.html[data management policy] -with a GemFire http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/ClientRegionShortcut.html[ClientRegionShortcut] +with a GemFire http://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/ClientRegionShortcut.html[ClientRegionShortcut] (default is `PROXY`). This attribute is only used when configuring client Region. * `poolName` - name of the dedicated GemFire Pool used to connect a client to the cluster of servers. The attribute is only used when the application is a GemFire cache client. Defaults to `gemfirePool`. @@ -230,7 +230,7 @@ Go ahead and view the cookies (click for help with https://developer.chrome.com/ or https://getfirebug.com/wiki/index.php/Cookies_Panel#Cookies_List[Firefox]). NOTE: The following instructions assume you have a local GemFire installation. For more information on installation, -see http://gemfire.docs.pivotal.io/docs-gemfire/latest/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. +see http://gemfire.docs.pivotal.io/docs-gemfire/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. NOTE: In order to run the following, you must uncomment the lines in the `GemFireServer` class, `gemfireProperties` bean for the following GemFire System properties: `jmx-manager` and `jmx-manager-start`. diff --git a/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver-xml.adoc b/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver-xml.adoc index 6e3c29df..73db8822 100644 --- a/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver-xml.adoc +++ b/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver-xml.adoc @@ -92,7 +92,7 @@ bean to replace placeholders in the Spring XML configuration meta-data with the at the designated host/port is running and listening for client connections, blocking client startup until the server is available and ready. <4> Next, we include a `Properties` bean to configure certain aspects of the GemFire client cache using -http://gemfire.docs.pivotal.io/docs-gemfire/reference/topics/gemfire_properties.html[GemFire's System Properties]. +http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/gemfire_properties.html[GemFire's System Properties]. In this case, we are just setting GemFire's `log-level` from a application-specific System property, defaulting to `warning` if unspecified. <5> Then we create a instance of a GemFire `ClientCache` initialized with our `gemfireProperties`. @@ -234,7 +234,7 @@ Go ahead and view the cookies (click for help with https://developer.chrome.com/ or https://getfirebug.com/wiki/index.php/Cookies_Panel#Cookies_List[Firefox]). NOTE: The following instructions assume you have a local GemFire installation. For more information on installation, -see http://gemfire.docs.pivotal.io/docs-gemfire/latest/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. +see https://gemfire.docs.pivotal.io/gemfire/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. If you like, you can easily remove the session using `gfsh`. For example, on a Linux-based system type the following at the command-line: diff --git a/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver.adoc b/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver.adoc index 86055248..9ec80fbd 100644 --- a/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver.adoc +++ b/docs/src/docs/asciidoc/guides/httpsession-gemfire-clientserver.adoc @@ -87,12 +87,12 @@ include::{samples-dir}httpsession-gemfire-clientserver/src/main/java/sample/Clie implements `Filter`. The filter is what replaces the `HttpSession` with an implementation backed by Spring Session and GemFire. <2> Next, we register a `Properties` bean that allows us to configure certain aspects of the GemFire client cache -using http://gemfire.docs.pivotal.io/docs-gemfire/reference/topics/gemfire_properties.html[GemFire's System properties]. +using http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/gemfire_properties.html[GemFire's System properties]. <3> We use the `Properties` to configure an instance of a GemFire `ClientCache`. <4> Then, we configure a `Pool` of client connections to talk to the GemFire Server in our Client/Server topology. In our configuration, we have used sensible settings for timeouts, number of connections and so on. Also, the `Pool` has been configured to connect directly to a server. Learn more about various `Pool` configuration settings from the -http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/PoolFactory.html[PoolFactory API]. +http://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/PoolFactory.html[PoolFactory API]. <56> Finally, we include a Spring `BeanPostProcessor` to block the client until our GemFire Server is up and running, listening for and accepting client connections. @@ -100,7 +100,7 @@ The `gemfireCacheServerReadyBeanPostProcessor` is necessary in order to coordina an automated fashion during testing, but unnecessary in situations where the GemFire cluster is already presently running, such as in production. -The `BeanPostProcessor` uses a GemFire http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/management/membership/ClientMembershipListener.html[ClientMembershipListener] +The `BeanPostProcessor` uses a GemFire https://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/management/membership/ClientMembershipListener.html[ClientMembershipListener] that will be notified when the client has successfully connected to the server. Once a connection has been established, the listener releases the latch that the `BeanPostProcessor` will wait on (up to the specified timeout) in the `postProcessAfterInitialization` callback to block the client. @@ -118,7 +118,7 @@ and GemFire out-of-the-box using the following attributes: * `maxInactiveIntervalInSeconds` - controls _HttpSession_ idle-timeout expiration (defaults to **30 minutes**). * `regionName` - specifies the name of the GemFire Region used to store `HttpSession` state (defaults is "*ClusteredSpringSessions*"). * `clientRegionShort` - specifies GemFire's http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/management_all_region_types/chapter_overview.html[data management policy] -with a GemFire http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/ClientRegionShortcut.html[ClientRegionShortcut] +with a GemFire https://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/ClientRegionShortcut.html[ClientRegionShortcut] (default is `PROXY`). This attribute is only used when configuring client Region. * `poolName` - name of the dedicated GemFire Pool used to connect a client to the cluster of servers. The attribute is only used when the application is a GemFire cache client. Defaults to `gemfirePool`. @@ -233,7 +233,7 @@ Go ahead and view the cookies (click for help with https://developer.chrome.com/ or https://getfirebug.com/wiki/index.php/Cookies_Panel#Cookies_List[Firefox]). NOTE: The following instructions assume you have a local GemFire installation. For more information on installation, -see http://gemfire.docs.pivotal.io/docs-gemfire/latest/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. +see https://gemfire.docs.pivotal.io/gemfire/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. If you like, you can easily remove the session using `gfsh`. For example, on a Linux-based system type the following at the command-line: diff --git a/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p-xml.adoc b/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p-xml.adoc index 7b22274d..fa7ea42f 100644 --- a/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p-xml.adoc +++ b/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p-xml.adoc @@ -176,7 +176,7 @@ Go ahead and view the cookies (click for help with https://developer.chrome.com/ or https://getfirebug.com/wiki/index.php/Cookies_Panel#Cookies_List[Firefox]). NOTE: The following instructions assume you have a local GemFire installation. For more information on installation, -see http://gemfire.docs.pivotal.io/docs-gemfire/latest/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. +see http://gemfire.docs.pivotal.io/gemfire/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. If you like, you can easily remove the session using `gfsh`. For example, on a Linux-based system type the following at the command-line: diff --git a/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p.adoc b/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p.adoc index c452383f..d78f861c 100644 --- a/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p.adoc +++ b/docs/src/docs/asciidoc/guides/httpsession-gemfire-p2p.adoc @@ -104,7 +104,7 @@ and GemFire out-of-the-box using the following attributes: * `maxInactiveIntervalInSeconds` - controls HttpSession idle-timeout expiration (defaults to **30 minutes**). * `regionName` - specifies the name of the GemFire Region used to store `HttpSession` state (defaults is "_ClusteredSpringSessions_"). * `serverRegionShort` - specifies GemFire http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/management_all_region_types/chapter_overview.html[data management policies] -with a GemFire http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/RegionShortcut.html[RegionShortcut] +with a GemFire https://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/RegionShortcut.html[RegionShortcut] (default is `PARTITION`). NOTE: `clientRegionShort` is ignored in a peer cache configuration and only applies when a client-server topology, @@ -175,7 +175,7 @@ Go ahead and view the cookies (click for help with https://developer.chrome.com/ or https://getfirebug.com/wiki/index.php/Cookies_Panel#Cookies_List[Firefox]). NOTE: The following instructions assume you have a local GemFire installation. For more information on installation, -see http://gemfire.docs.pivotal.io/docs-gemfire/latest/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. +see https://gemfire.docs.pivotal.io/gemfire/getting_started/installation/install_intro.html[Installing Pivotal GemFire]. If you like, you can easily remove the session using `gfsh`. For example, on a Linux-based system type the following at the command-line: diff --git a/docs/src/docs/asciidoc/index.adoc b/docs/src/docs/asciidoc/index.adoc index a9c13559..bc907215 100644 --- a/docs/src/docs/asciidoc/index.adoc +++ b/docs/src/docs/asciidoc/index.adoc @@ -192,7 +192,7 @@ The two most common topologies to manage Spring Sessions using GemFire include: * <> * <> -Additionally, GemFire supports site-to-site replication using https://gemfire.docs.pivotal.io/geode/topologies_and_comm/multi_site_configuration/chapter_overview.html[WAN functionality]. +Additionally, GemFire supports site-to-site replication using http://gemfire.docs.pivotal.io/docs-gemfire/latest/topologies_and_comm/multi_site_configuration/chapter_overview.html[WAN functionality]. The ability to configure and use GemFire's WAN support is independent of Spring Session, and is beyond the scope of this document. More details on GemFire WAN functionality can be found http://docs.spring.io/spring-data-gemfire/docs/current/reference/html/#bootstrap:gateway[here].