This repository was archived by the owner on Apr 4, 2025. It is now read-only.
Align WebSession#save implementations with API clarifications #47
Comments
gregturn
added a commit
that referenced
this issue
Jan 16, 2019
Only perform a save after verifying the MongoSession already exists in MongoDB. Otherwise, throw an IllegalStateException. Resolved #47.
gregturn
added a commit
that referenced
this issue
Jan 16, 2019
Only perform a save after verifying the MongoSession already exists in MongoDB. Otherwise, throw an IllegalStateException. Resolved #47.
|
Digging deeper, it appears that |
gregturn
added a commit
that referenced
this issue
Jan 16, 2019
Only perform a save after verifying the MongoSession already exists in MongoDB. Otherwise, throw an IllegalStateException. Resolved #47.
gregturn
added a commit
that referenced
this issue
Jan 16, 2019
Introduce new state to MongoSession denoting if a session is new or not. Only perform a save on a non-new MongoSession if it already exists in the MongoDB. Otherwise, throw an IllegalStateException. Resolved #47.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See spring-projects/spring-session#1135 - looking at the implementation of
ReactiveMongoOperationsSessionRepositoryit doesn't appear to comply with theWebSession#saveAPI.The text was updated successfully, but these errors were encountered: