Attempt to generalize context propagation pattern #1
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.
See introduction comment in the issue: ...
Implementation details:
org.springframework.security.concurrent
package toorg.springframework.util.concurrent
(to be easy-movable to spring-core)org.springframework.security.concurrent
org.springframework.security.concurrent
are kept existing, for backward compatibility reasons (e.g.DelegatingSecurityContextRunnable
is not actually needed any more, and can be removed in favor ofDelegatingContextRunnable
, but is kept)SecurityContextOps
implementation ofContextOps
is used to incapsulate and provide security-specific behaviorContextOps
andSecurityContextHolderStrategy
are pretty similar, but probably should be kept both (one for backward-compatibility, another - to be moved in spring-core)Haven't done yet:
DelegatingSecurityContextAsyncTaskExecutor
DelegatingSecurityContextTaskExecutor
(right now they extend specific base classes)