Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-9187

LockOperation always calls SessionDelegate.refresh before executing operations

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.38.0
    • Component/s: jcr
    • Labels:
      None

      Description

      Antonio Sanso reported that calls to LockManager.isLocked (or Node.isLocked) always results in the session being forcefully refreshed. This is inconsistent with other JCR level read operations which either don't refresh at all or only refresh in the SessionDelegate#prePerform if the RefreshStrategy in place mandates it.

      The same seems to apply for those lock-related methods that include write: The session is always refreshed upon entering the methods, while other write operations either delegate refresh to the RefreshStrategy or only refresh once changes have been committed to the underlying Root.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              angela Angela Schreiber

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment