This product enables applications to use Spring Session
with MongoDB and provides a SessionRepository implementation backed
by MongoDB using Spring Data MongoDB.
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. It also provides transparent integration with:
HttpSession- allows replacing theHttpSessionin an application container (i.e. Tomcat) neutral way, with support for providing session IDs in headers to work with RESTful APIs.WebSocket- provides the ability to keep theHttpSessionalive when receiving WebSocket messagesWebSession- allows replacing the Spring WebFlux'sWebSessionin an application container neutral way.
The API namespace has changed from org.springframework.session.data.mongo to org.mongodb.spring.session.
As per the wider changes in the Spring framework, Jackson 2 support is deprecated and Jackson 3 support has been added:
- Jackson 2 support is now deprecated and is available via
Jackson2MongoSessionConverter - Jackson 3 support is now available via
JacksonMongoSessionConverter
For issues with, questions about, or feedback for the MongoDB Java, Kotlin, and Scala drivers, please look into our support channels. Please do not email any of the driver developers directly with issues or questions - you're more likely to get an answer on StackOverflow.
At a minimum, please include in your description the exact version of the library and any dependencies that you are using.
Think you’ve found a bug? Want to see a new feature in the MongoDB Spring Session? Please open a case in our issue management tool, JIRA:
- Create an account and login.
- Navigate to the JAVA Frameworks project.
- Click Create Issue - Please provide as much information as possible about the issue type, which driver you are using, and how to reproduce your issue.
Bug reports in JIRA for the extension and the Core Server (i.e. SERVER) project are public.
If you’ve identified a security vulnerability in the library or any other MongoDB project, please report it according to the instructions here.
We follow semantic versioning when releasing.
Binaries and dependency information for Maven, Gradle, Ivy and others can be found at https://central.sonatype.com/search.
Example for Maven:
<dependency>
<groupId>org.mongodb</groupId>
<artifactId>mongo-spring-session</artifactId>
<version>x.y.z</version>
</dependency>Snapshot builds are also published regulary via Sonatype.
Example for Maven:
<repositories>
<repository>
<name>Central Portal Snapshots</name>
<id>central-portal-snapshots</id>
<url>https://central.sonatype.com/repository/maven-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>This project uses separate directories for unit and integration tests:
./gradlew clean check./gradlew clean test./gradlew clean integrationTestIntegration tests require a MongoDB deployment to be available
This project uses evergreen, a distributed continuous integration system from MongoDB. The evergreen configuration is in the .evergreen directory.