XWIKI-22665: Required rights should be cached #3695
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.
Jira URL
https://jira.xwiki.org/browse/XWIKI-22665
Changes
Description
DocumentRequiredRightsManager
from the page test component list and instead add a mock inMockitoOldcore
.DocumentRequiredRightsManager
to the authorization bridge as it fits better there and with the mock implementation inMockitoOldcore
there is no need to have it available for tests.Clarifications
DocumentCache
as the internal logic for having several values per key vastly exceeds the memory requirements of the required rights cache.Screenshots & Video
No UI changes.
Executed Tests
Manual test of the changed modules in a 17.0.0-SNAPSHOT demo instance.
Expected merging strategy