Fix SessionCreatedEvent handling in RedisIndexedSessionRepository #2171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While attempting to migrate
RedisIndexedSessionRepository
toRedisSessionMapper
in order to reuse the session mapping logic, I ran into #1338. This problem has been somewhat hidden by the old mapping code being too lenient and accepting a map with no entries at all whereasRedisSessionMapper
validates both map not being empty as well as presence of key session properties.At present,
RedisIndexedSessionRepository
publishes aSessionCreatedEvent
backed by an emptyMapSession
instance. This happens because session delta has been cleared before publishing a message to the session created channel.Fixes gh-1338