Repository navigation
Define loopback behavior for Lock annotation - #899
Merged
Merged
Conversation
Open
KyleAure
reviewed
Jul 21, 2026
KyleAure
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds language to the Javadoc of
@Lockaddressing what happens when a method invokes another method of a bean that has a lock, taking into account the possibility that the lock and requested lock might differ in READ vs WRITE mode.The discussion of this was started by @arjantijms in #135 (comment) of issue #135 . In the subsequent comments we decided that an attempt to upgrade from READ to WRITE should fail fast.