Spring Session MongoDB provides a solution for Spring Session in a MongoDB data store.
-
Accessing a session from any environment (i.e. web, messaging infrastructure, etc)
-
In a web environment
-
Support for clustering in a vendor neutral way
-
Pluggable strategy for determining the session id
-
Easily keep the HttpSession alive when a WebSocket is active
-
We go to great lengths to ensure smooth upgrades. We also seek to make your upgrade on major versions of Java can be as smooth as possible.
Check the matrix below to see the status of supported versions:
| Job | master branch (2.1) |
2.0.x branch (2.0.x) |
|---|---|---|
Test - JDK 8 |
||
Test - JDK 8 and Spring.NEXT |
||
Test - JDK 8 and Spring.NEXT 5.1 |
||
Test - JDK 8 and Spring Data.NEXT |
||
Test - JDK 11 |
||
Test - JDK 11 and Spring.NEXT |
||
Test - JDK 11 and Spring.NEXT 5.1 |
||
Test - JDK 11 and Spring Data.NEXT |
||
Test - JDK 12* |
||
Test - JDK 12* and Spring.NEXT |
||
Test - JDK 12* and Spring.NEXT 5.1 |
||
Test - JDK 12* and Spring Data.NEXT |
||
Build - Release to repo.spring.io |
|
Important
|
Spring Session for MongoDB 2.1 runs on Spring Framework 5.1, which has support for JDK 11. Spring Session for MongoDB 2.0.x runs on Spring Framework 5.0 and is NOT supported on JDK 11 despite our pipelines testing against it. The extra tests are designed to give you a smooth upgrade path. If you are going into production on JDK 11, should need to be using Spring Session for MongoDB 2.1. |
|
Important
|
JDK 12 is Java’s latest version and is unstable. We are testing against it to catch issues early on, but don’t support it directly on any version of Spring Session for MongoDB. |
-
Run
mvn clean package
This will generate the artifact.
You can also import the project into your IDE.
To do a release (.RELEASE, .RC?, .M?):
-
Check in all changes and ensure there are no edited files.
-
Run
ci/create-release.sh <release version> <snapshot version>e.g. (ci/create-release.sh 2.1.1.RELEASE 2.1.2.BUILD-SNAPSHOT)
From here, test things out locally.
-
git checkout release -
./mvn clean package -
…do all your testing…
Once verified, push the release branch to origin and let the CI server deploy it.
-
git push
After a clean release, switch back to master branch and push the master development branch.
-
git checkout master -
git push -
git push --tags
CI server should build the new snapshot and automatically deploy to artifactory.
|
Note
|
A word about reference documentation. Based upon this, the distribute profile contains an artifactory property that is applied to the ZIP file generated by the docs profile. A CRON job will scoop up the zipped up docs and unpack them inside the target location.
|
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
You can find the documentation, issue management, support, samples, and guides for using Spring Session MongoDB at https://projects.spring.io/spring-session-data-mongodb/
Spring Session is Open Source software released under the Apache 2.0 license.