187 lines
6.8 KiB
Plaintext
187 lines
6.8 KiB
Plaintext
= Spring Session - HttpSession (Quick Start)
|
|
Rob Winch, Vedran Pavić
|
|
:stylesdir: ../
|
|
:highlightjsdir: ../js/highlight
|
|
:docinfodir: guides
|
|
|
|
This guide describes how to use Spring Session to transparently leverage a relational to back a web application's `HttpSession` with XML based configuration.
|
|
|
|
NOTE: You can find the completed guide in the <<httpsession-jdbc-xml-sample, httpsession-jdbc-xml sample application>>.
|
|
|
|
[#index-link]
|
|
link:../index.html[Index]
|
|
|
|
== Updating Dependencies
|
|
|
|
Before you use Spring Session, you must update your dependencies.
|
|
If you are using Maven, you must add the following dependencies:
|
|
|
|
====
|
|
.pom.xml
|
|
[source,xml]
|
|
[subs="verbatim,attributes"]
|
|
----
|
|
<dependencies>
|
|
<!-- ... -->
|
|
|
|
<dependency>
|
|
<groupId>org.springframework.session</groupId>
|
|
<artifactId>spring-session-jdbc</artifactId>
|
|
<version>{spring-session-version}</version>
|
|
<type>pom</type>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>org.springframework</groupId>
|
|
<artifactId>spring-web</artifactId>
|
|
<version>{spring-framework-version}</version>
|
|
</dependency>
|
|
</dependencies>
|
|
----
|
|
====
|
|
|
|
ifeval::["{version-snapshot}" == "true"]
|
|
Since we are using a SNAPSHOT version, we need to add the Spring Snapshot Maven Repository.
|
|
You must have the following in your pom.xml:
|
|
|
|
====
|
|
.pom.xml
|
|
[source,xml]
|
|
----
|
|
<repositories>
|
|
|
|
<!-- ... -->
|
|
|
|
<repository>
|
|
<id>spring-snapshot</id>
|
|
<url>https://repo.spring.io/libs-snapshot</url>
|
|
</repository>
|
|
</repositories>
|
|
----
|
|
====
|
|
endif::[]
|
|
|
|
ifeval::["{version-milestone}" == "true"]
|
|
Since we are using a Milestone version, we need to add the Spring Milestone Maven Repository.
|
|
You must have the following in your pom.xml:
|
|
|
|
====
|
|
.pom.xml
|
|
[source,xml]
|
|
----
|
|
<repository>
|
|
<id>spring-milestone</id>
|
|
<url>https://repo.spring.io/libs-milestone</url>
|
|
</repository>
|
|
----
|
|
====
|
|
endif::[]
|
|
|
|
// tag::config[]
|
|
|
|
[[httpsession-jdbc-xml-spring-configuration]]
|
|
== Spring XML Configuration
|
|
|
|
After adding the required dependencies, we can create our Spring configuration.
|
|
The Spring configuration is responsible for creating a servlet filter that replaces the `HttpSession` implementation with an implementation backed by Spring Session.
|
|
The following listing shows how to add the following Spring Configuration:
|
|
|
|
====
|
|
.src/main/webapp/WEB-INF/spring/session.xml
|
|
[source,xml,indent=0]
|
|
----
|
|
include::{samples-dir}spring-session-sample-xml-jdbc/src/main/webapp/WEB-INF/spring/session.xml[tags=beans]
|
|
----
|
|
|
|
<1> We use the combination of `<context:annotation-config/>` and `JdbcHttpSessionConfiguration` because Spring Session does not yet provide XML Namespace support (see https://github.com/spring-projects/spring-session/issues/104[gh-104]).
|
|
This creates a Spring bean with the name of `springSessionRepositoryFilter`.
|
|
That bean implements `Filter`.
|
|
The filter is in charge of replacing the `HttpSession` implementation to be backed by Spring Session.
|
|
In this instance, Spring Session is backed by a relational database.
|
|
<2> We create a `dataSource` that connects Spring Session to an embedded instance of an H2 database.
|
|
We configure the H2 database to create database tables by using the SQL script that is included in Spring Session.
|
|
<3> We create a `transactionManager` that manages transactions for previously configured `dataSource`.
|
|
====
|
|
|
|
For additional information on how to configure data access-related concerns, see the https://docs.spring.io/spring/docs/{spring-framework-version}/spring-framework-reference/data-access.html[Spring Framework Reference Documentation].
|
|
|
|
== XML Servlet Container Initialization
|
|
|
|
Our <<httpsession-jdbc-xml-spring-configuration,Spring Configuration>> created a Spring bean named `springSessionRepositoryFilter` that implements `Filter`.
|
|
The `springSessionRepositoryFilter` bean is responsible for replacing the `HttpSession` with a custom implementation that is backed by Spring Session.
|
|
|
|
In order for our `Filter` to do its magic, we need to instruct Spring to load our `session.xml` configuration.
|
|
We do so with the following configuration:
|
|
|
|
====
|
|
.src/main/webapp/WEB-INF/web.xml
|
|
[source,xml,indent=0]
|
|
----
|
|
include::{samples-dir}spring-session-sample-xml-jdbc/src/main/webapp/WEB-INF/web.xml[tags=context-param]
|
|
include::{samples-dir}spring-session-sample-xml-jdbc/src/main/webapp/WEB-INF/web.xml[tags=listeners]
|
|
----
|
|
====
|
|
|
|
The https://docs.spring.io/spring/docs/{spring-framework-version}/spring-framework-reference/core.html#context-create[`ContextLoaderListener`] reads the `contextConfigLocation` and picks up our session.xml configuration.
|
|
|
|
Last, we need to ensure that our Servlet Container (that is, Tomcat) uses our `springSessionRepositoryFilter` for every request.
|
|
The following snippet performs this last step for us:
|
|
|
|
====
|
|
.src/main/webapp/WEB-INF/web.xml
|
|
[source,xml,indent=0]
|
|
----
|
|
include::{samples-dir}spring-session-sample-xml-jdbc/src/main/webapp/WEB-INF/web.xml[tags=springSessionRepositoryFilter]
|
|
----
|
|
====
|
|
|
|
The https://docs.spring.io/spring-framework/docs/{spring-framework-version}/javadoc-api/org/springframework/web/filter/DelegatingFilterProxy.html[`DelegatingFilterProxy`] looks up a bean named `springSessionRepositoryFilter` and casts it to a `Filter`.
|
|
For every request on which `DelegatingFilterProxy` is invoked, the `springSessionRepositoryFilter` is invoked.
|
|
|
|
// end::config[]
|
|
|
|
[[httpsession-jdbc-xml-sample]]
|
|
== `httpsession-jdbc-xml` Sample Application
|
|
|
|
This section describes how to work with the `httpsession-jdbc-xml` Sample Application.
|
|
|
|
=== Running the `httpsession-jdbc-xml` Sample Application
|
|
|
|
You can run the sample by obtaining the {download-url}[source code] and invoking the following command:
|
|
|
|
====
|
|
----
|
|
$ ./gradlew :spring-session-sample-xml-jdbc:tomcatRun
|
|
----
|
|
====
|
|
|
|
You should now be able to access the application at http://localhost:8080/
|
|
|
|
=== Exploring the `httpsession-jdbc-xml` Sample Application
|
|
|
|
Now you can try using the application. To do so, fill out the form with the following information:
|
|
|
|
* *Attribute Name:* _username_
|
|
* *Attribute Value:* _rob_
|
|
|
|
Now click the *Set Attribute* button. You should now see the values displayed in the table.
|
|
|
|
=== How Does It Work?
|
|
|
|
We interact with the standard `HttpSession` in the following `SessionServlet`:
|
|
|
|
====
|
|
.src/main/java/sample/SessionServlet.java
|
|
[source,java]
|
|
----
|
|
include::{samples-dir}spring-session-sample-xml-jdbc/src/main/java/sample/SessionServlet.java[tags=class]
|
|
----
|
|
====
|
|
|
|
Instead of using Tomcat's `HttpSession`, we persist the values in the H2 database.
|
|
Spring Session creates a cookie named `SESSION` in your browser. That cookie contains the ID of your session.
|
|
You can view the cookies (with https://developers.google.com/web/tools/chrome-devtools/manage-data/cookies[Chrome] or https://developer.mozilla.org/en-US/docs/Tools/Storage_Inspector[Firefox]).
|
|
|
|
You can remove the session by using H2 web console available at: http://localhost:8080/h2-console/ (use `jdbc:h2:mem:testdb` for JDBC URL)
|
|
|
|
Now you can visit the application at http://localhost:8080/ and observe that the attribute we added is no longer displayed.
|