Skip to content

Commit 764fc4e

Browse files
committed
<<>> to xref
1 parent 26419e2 commit 764fc4e

File tree

6 files changed

+24
-24
lines changed

6 files changed

+24
-24
lines changed

spring-session-docs/modules/ROOT/pages/api.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ If the `Session` were expired, the result would be null.
6868
A `SessionRepository` is in charge of creating, retrieving, and persisting `Session` instances.
6969

7070
If possible, you should not interact directly with a `SessionRepository` or a `Session`.
71-
Instead, developers should prefer interacting with `SessionRepository` and `Session` indirectly through the <<httpsession,`HttpSession`>> and <<websocket,WebSocket>> integration.
71+
Instead, developers should prefer interacting with `SessionRepository` and `Session` indirectly through the xref:http-session.adoc#httpsession[`HttpSession`] and xref:web-socket.adoc#websocket[WebSocket] integration.
7272

7373
[[api-findbyindexnamesessionrepository]]
7474
== Using `FindByIndexNameSessionRepository`
@@ -110,7 +110,7 @@ include::{docs-test-dir}docs/FindByIndexNameSessionRepositoryTests.java[tags=fin
110110
A `ReactiveSessionRepository` is in charge of creating, retrieving, and persisting `Session` instances in a non-blocking and reactive manner.
111111

112112
If possible, you should not interact directly with a `ReactiveSessionRepository` or a `Session`.
113-
Instead, you should prefer interacting with `ReactiveSessionRepository` and `Session` indirectly through the <<websession,WebSession>> integration.
113+
Instead, you should prefer interacting with `ReactiveSessionRepository` and `Session` indirectly through the xref:web-session.adoc#websession[WebSession] integration.
114114

115115
[[api-enablespringhttpsession]]
116116
== Using `@EnableSpringHttpSession`
@@ -173,7 +173,7 @@ For additional information on how to create a `RedisConnectionFactory`, see the
173173
=== Using `@EnableRedisHttpSession`
174174

175175
In a web environment, the simplest way to create a new `RedisIndexedSessionRepository` is to use `@EnableRedisHttpSession`.
176-
You can find complete example usage in the <<samples>>.
176+
You can find complete example usage in the xref:samples.adoc#samples[].
177177
You can use the following attributes to customize the configuration:
178178

179179
* *maxInactiveIntervalInSeconds*: The amount of time before the session expires, in seconds.
@@ -493,7 +493,7 @@ include::{indexdoc-tests}[tags=new-mapsessionrepository]
493493
[[api-mapsessionrepository-hazelcast]]
494494
=== Using Spring Session and Hazlecast
495495

496-
The <<samples,Hazelcast Sample>> is a complete application that demonstrates how to use Spring Session with Hazelcast.
496+
The xref:samples.adoc#samples[Hazelcast Sample] is a complete application that demonstrates how to use Spring Session with Hazelcast.
497497

498498
To run it, use the following command:
499499

@@ -503,7 +503,7 @@ To run it, use the following command:
503503
----
504504
====
505505

506-
The <<samples,Hazelcast Spring Sample>> is a complete application that demonstrates how to use Spring Session with Hazelcast and Spring Security.
506+
The xref:samples.adoc#samples[Hazelcast Spring Sample] is a complete application that demonstrates how to use Spring Session with Hazelcast and Spring Security.
507507

508508
It includes example Hazelcast `MapListener` implementations that support firing `SessionCreatedEvent`, `SessionDeletedEvent`, and `SessionExpiredEvent`.
509509

@@ -547,7 +547,7 @@ For additional information on how to create and configure `JdbcTemplate` and `Pl
547547
=== Using `@EnableJdbcHttpSession`
548548

549549
In a web environment, the simplest way to create a new `JdbcIndexedSessionRepository` is to use `@EnableJdbcHttpSession`.
550-
You can find complete example usage in the <<samples>>
550+
You can find complete example usage in the xref:samples.adoc#samples[]
551551
You can use the following attributes to customize the configuration:
552552

553553
* *tableName*: The name of database table used by Spring Session to store sessions
@@ -622,7 +622,7 @@ For additional information on how to create and configure Hazelcast instance, se
622622
To use https://hazelcast.org/[Hazelcast] as your backing source for the `SessionRepository`, you can add the `@EnableHazelcastHttpSession` annotation to a `@Configuration` class.
623623
Doing so extends the functionality provided by the `@EnableSpringHttpSession` annotation but makes the `SessionRepository` for you in Hazelcast.
624624
You must provide a single `HazelcastInstance` bean for the configuration to work.
625-
You can find a complete configuration example in the <<samples>>.
625+
You can find a complete configuration example in the xref:samples.adoc#samples[].
626626

627627
[[api-enablehazelcasthttpsession-customize]]
628628
=== Basic Customization
@@ -641,7 +641,7 @@ Using a `MapListener` to respond to entries being added, evicted, and removed fr
641641

642642
Sessions are stored in a distributed `IMap` in Hazelcast.
643643
The `IMap` interface methods are used to `get()` and `put()` Sessions.
644-
Additionally, the `values()` method supports a `FindByIndexNameSessionRepository#findByIndexNameAndIndexValue` operation, together with appropriate `ValueExtractor` (which needs to be registered with Hazelcast). See the <<samples, Hazelcast Spring Sample>> for more details on this configuration.
644+
Additionally, the `values()` method supports a `FindByIndexNameSessionRepository#findByIndexNameAndIndexValue` operation, together with appropriate `ValueExtractor` (which needs to be registered with Hazelcast). See the xref:samples.adoc#samples[ Hazelcast Spring Sample] for more details on this configuration.
645645
The expiration of a session in the `IMap` is handled by Hazelcast's support for setting the time to live on an entry when it is `put()` into the `IMap`. Entries (sessions) that have been idle longer than the time to live are automatically removed from the `IMap`.
646646

647647
You should not need to configure any settings such as `max-idle-seconds` or `time-to-live-seconds` for the `IMap` within the Hazelcast configuration.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ with the same `SerializerConfiguration` of members.
111111

112112
== Servlet Container Initialization
113113

114-
Our <<security-spring-configuration,Spring Configuration>> created a Spring bean named `springSessionRepositoryFilter` that implements `Filter`.
114+
Our xref:guides/java-security.adoc#security-spring-configuration[Spring Configuration] created a Spring bean named `springSessionRepositoryFilter` that implements `Filter`.
115115
The `springSessionRepositoryFilter` bean is responsible for replacing the `HttpSession` with a custom implementation that is backed by Spring Session.
116116

117117
In order for our `Filter` to do its magic, Spring needs to load our `SessionConfig` class.

spring-session-docs/modules/ROOT/pages/http-session.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can choose from enabling this by using either:
2626

2727
This section describes how to use Redis to back `HttpSession` by using Java based configuration.
2828

29-
NOTE: The <<samples, HttpSession Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
29+
NOTE: The xref:samples.adoc#samples[ HttpSession Sample] provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
3030
You can read the basic steps for integration in the next few sections, but we encourage you to follow along with the detailed HttpSession Guide when integrating with your own application.
3131

3232
include::guides/java-redis.adoc[tags=config,leveloffset=+2]
@@ -36,7 +36,7 @@ include::guides/java-redis.adoc[tags=config,leveloffset=+2]
3636

3737
This section describes how to use Redis to back `HttpSession` by using XML based configuration.
3838

39-
NOTE: The <<samples, HttpSession XML Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` using XML configuration.
39+
NOTE: The xref:samples.adoc#samples[ HttpSession XML Sample] provides a working sample of how to integrate Spring Session and `HttpSession` using XML configuration.
4040
You can read the basic steps for integration in the next few sections, but we encourage you to follow along with the detailed HttpSession XML Guide when integrating with your own application.
4141

4242
include::guides/xml-redis.adoc[tags=config,leveloffset=+2]
@@ -56,7 +56,7 @@ You can choose to do in any of the following ways:
5656

5757
This section describes how to use a relational database to back `HttpSession` when you use Java-based configuration.
5858

59-
NOTE: The <<samples, HttpSession JDBC Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
59+
NOTE: The xref:samples.adoc#samples[ HttpSession JDBC Sample] provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
6060
You can read the basic steps for integration in the next few sections, but we encouraged you to follow along with the detailed HttpSession JDBC Guide when integrating with your own application.
6161

6262
include::guides/java-jdbc.adoc[tags=config,leveloffset=+2]
@@ -66,7 +66,7 @@ include::guides/java-jdbc.adoc[tags=config,leveloffset=+2]
6666

6767
This section describes how to use a relational database to back `HttpSession` when you use XML based configuration.
6868

69-
NOTE: The <<samples, HttpSession JDBC XML Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` by using XML configuration.
69+
NOTE: The xref:samples.adoc#samples[ HttpSession JDBC XML Sample] provides a working sample of how to integrate Spring Session and `HttpSession` by using XML configuration.
7070
You can read the basic steps for integration in the next few sections, but we encourage you to follow along with the detailed HttpSession JDBC XML Guide when integrating with your own application.
7171

7272
include::guides/xml-jdbc.adoc[tags=config,leveloffset=+2]
@@ -76,7 +76,7 @@ include::guides/xml-jdbc.adoc[tags=config,leveloffset=+2]
7676

7777
This section describes how to use a relational database to back `HttpSession` when you use Spring Boot.
7878

79-
NOTE: The <<samples, HttpSession JDBC Spring Boot Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` by using Spring Boot.
79+
NOTE: The xref:samples.adoc#samples[ HttpSession JDBC Spring Boot Sample] provides a working sample of how to integrate Spring Session and `HttpSession` by using Spring Boot.
8080
You can read the basic steps for integration in the next few sections, but we encourage you to follow along with the detailed HttpSession JDBC Spring Boot Guide when integrating with your own application.
8181

8282
include::guides/boot-jdbc.adoc[tags=config,leveloffset=+2]
@@ -88,7 +88,7 @@ Using Spring Session with `HttpSession` is enabled by adding a Servlet Filter be
8888

8989
This section describes how to use Hazelcast to back `HttpSession` by using Java-based configuration.
9090

91-
NOTE: The <<samples, Hazelcast Spring Sample>> provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
91+
NOTE: The xref:samples.adoc#samples[ Hazelcast Spring Sample] provides a working sample of how to integrate Spring Session and `HttpSession` by using Java configuration.
9292
You can read the basic steps for integration in the next few sections, but we encourage you to follow along with the detailed Hazelcast Spring Guide when integrating with your own application.
9393

9494
include::guides/java-hazelcast.adoc[tags=config,leveloffset=+1]
@@ -158,7 +158,7 @@ This highlights why it is important that Spring Session's `SessionRepositoryFilt
158158

159159
Spring Session can work with RESTful APIs by letting the session be provided in a header.
160160

161-
NOTE: The <<samples, REST Sample>> provides a working sample of how to use Spring Session in a REST application to support authenticating with a header.
161+
NOTE: The xref:samples.adoc#samples[ REST Sample] provides a working sample of how to use Spring Session in a REST application to support authenticating with a header.
162162
You can follow the basic steps for integration described in the next few sections, but we encourage you to follow along with the detailed REST Guide when integrating with your own application.
163163

164164
include::guides/java-rest.adoc[tags=config,leveloffset=+1]

spring-session-docs/modules/ROOT/pages/index.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -59,8 +59,8 @@ The minimum requirements for Spring Session are:
5959
* Java 8+.
6060
* If you run in a Servlet Container (not required), Servlet 3.1+.
6161
* If you use other Spring libraries (not required), the minimum required version is Spring 5.0.x.
62-
* `@EnableRedisHttpSession` requires Redis 2.8+. This is necessary to support <<api-redisindexedsessionrepository-expiration,Session Expiration>>
63-
* `@EnableHazelcastHttpSession` requires Hazelcast 3.6+. This is necessary to support <<api-enablehazelcasthttpsession-storage,`FindByIndexNameSessionRepository`>>
62+
* `@EnableRedisHttpSession` requires Redis 2.8+. This is necessary to support xref:api.adoc#api-redisindexedsessionrepository-expiration[Session Expiration]
63+
* `@EnableHazelcastHttpSession` requires Hazelcast 3.6+. This is necessary to support xref:api.adoc#api-enablehazelcasthttpsession-storage[`FindByIndexNameSessionRepository`]
6464

6565
NOTE: At its core, Spring Session has a required dependency only on `spring-jcl`.
66-
For an example of using Spring Session without any other Spring dependencies, see the <<samples,hazelcast sample>> application.
66+
For an example of using Spring Session without any other Spring dependencies, see the xref:samples.adoc#samples[hazelcast sample] application.

spring-session-docs/modules/ROOT/pages/introduction.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,6 @@
44
Spring Session provides an API and implementations for managing a user's session information while also making it trivial to support clustered sessions without being tied to an application container-specific solution.
55
It also provides transparent integration with:
66

7-
* <<httpsession,HttpSession>>: Allows replacing the `HttpSession` in an application container-neutral way, with support for providing session IDs in headers to work with RESTful APIs.
8-
* <<websocket,WebSocket>>: Provides the ability to keep the `HttpSession` alive when receiving WebSocket messages
9-
* <<websession,WebSession>>: Allows replacing the Spring WebFlux's `WebSession` in an application container-neutral way.
7+
* xref:http-session.adoc#httpsession[HttpSession]: Allows replacing the `HttpSession` in an application container-neutral way, with support for providing session IDs in headers to work with RESTful APIs.
8+
* xref:web-socket.adoc#websocket[WebSocket]: Provides the ability to keep the `HttpSession` alive when receiving WebSocket messages
9+
* xref:web-session.adoc#websession[WebSession]: Allows replacing the Spring WebFlux's `WebSession` in an application container-neutral way.

spring-session-docs/modules/ROOT/pages/web-socket.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,12 @@ This means that, if we are actively chatting in our application and are not usin
2121
[[websocket-usage]]
2222
== WebSocket Usage
2323

24-
The <<samples, WebSocket Sample>> provides a working sample of how to integrate Spring Session with WebSockets.
24+
The xref:samples.adoc#samples[ WebSocket Sample] provides a working sample of how to integrate Spring Session with WebSockets.
2525
You can follow the basic steps for integration described in the next few headings, but we encourage you to follow along with the detailed WebSocket Guide when integrating with your own application.
2626

2727
[[websocket-httpsession]]
2828
=== `HttpSession` Integration
2929

30-
Before using WebSocket integration, you should be sure that you have <<httpsession>> working first.
30+
Before using WebSocket integration, you should be sure that you have xref:http-session.adoc#httpsession[] working first.
3131

3232
include::guides/boot-websocket.adoc[tags=config,leveloffset=+2]

0 commit comments

Comments
 (0)