Skip to content

Commit 9276e1d

Browse files
Merge branch '2.7.x'
2 parents a09146a + fab1f7b commit 9276e1d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

spring-session-docs/modules/ROOT/pages/guides/java-hazelcast.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Spring Session provides `PrincipalNameExtractor` for this purpose.
100100
is not set, Hazelcast will serialize sessions using native Java serialization.
101101
<4> We create a `HazelcastInstance` that connects Spring Session to Hazelcast.
102102
By default, the application starts and connects to an embedded instance of Hazelcast.
103-
For more information on configuring Hazelcast, see the https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#hazelcast-configuration[reference documentation].
103+
For more information on configuring Hazelcast, see the https://docs.hazelcast.com/hazelcast/latest/[reference documentation].
104104
====
105105

106106
NOTE: If `HazelcastSessionSerializer` is preferred, it needs to be configured for all Hazelcast cluster members before they start.
@@ -161,7 +161,7 @@ $ ./gradlew :spring-session-sample-javaconfig-hazelcast:tomcatRun
161161
====
162162

163163
NOTE: By default, Hazelcast runs in embedded mode with your application.
164-
However, if you want to connect to a standalone instance instead, you can configure it by following the instructions in the https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#hazelcast-configuration[reference documentation].
164+
However, if you want to connect to a standalone instance instead, you can configure it by following the instructions in the https://docs.hazelcast.com/hazelcast/latest/getting-started/get-started-cli[reference documentation].
165165

166166
You should now be able to access the application at http://localhost:8080/
167167

@@ -188,9 +188,9 @@ You can view the cookies (with https://developers.google.com/web/tools/chrome-de
188188

189189
=== Interacting with the Data Store
190190

191-
You can remove the session by using https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#hazelcast-java-client[a Java client],
192-
https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#other-client-implementations[one of the other clients], or the
193-
https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#management-center[management center].
191+
You can remove the session by using https://docs.hazelcast.com/hazelcast/latest/clients/java[a Java client],
192+
https://hazelcast.com/clients/[one of the other clients], or the
193+
https://docs.hazelcast.com/management-center/latest/getting-started/overview[management center].
194194

195195
==== Using the Console
196196

@@ -203,7 +203,7 @@ For example, to remove the session by using the management center console after
203203
----
204204
====
205205

206-
TIP: The Hazelcast documentation has instructions for https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#executing-console-commands[the console].
206+
TIP: The Hazelcast documentation has instructions for https://docs.hazelcast.com/hazelcast/latest/clients/clc[the console].
207207

208208
Alternatively, you can also delete the explicit key. Enter the following into the console, being sure to replace `7e8383a4-082c-4ffe-a4bc-c40fd3363c5e` with the value of your `SESSION` cookie:
209209

@@ -218,7 +218,7 @@ Now visit the application at http://localhost:8080/ and observe that we are no l
218218
==== Using the REST API
219219

220220
As described in the section of the documentation that cover other clients, there is a
221-
https://docs.hazelcast.org/docs/{hazelcast-version}/manual/html-single/index.html#rest-client[REST API]
221+
https://docs.hazelcast.com/hazelcast/latest/clients/rest[REST API]
222222
provided by the Hazelcast node(s).
223223

224224
For example, you could delete an individual key as follows (being sure to replace `7e8383a4-082c-4ffe-a4bc-c40fd3363c5e` with the value of your SESSION cookie):

0 commit comments

Comments
 (0)