[
https://issues.apache.org/jira/browse/OAK-9187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-9187.
-----------------------------------
Fix Version/s: 1.38.0
Resolution: Fixed
OK, sounds good to me.
Applied the patch and added the two tests to the know issues list:
http://svn.apache.org/r1885356
> LockOperation always calls SessionDelegate.refresh before executing operations
> ------------------------------------------------------------------------------
>
> Key: OAK-9187
> URL: https://issues.apache.org/jira/browse/OAK-9187
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Reporter: Angela Schreiber
> Priority: Major
> Fix For: 1.38.0
>
> Attachments: OAK-9187.patch
>
>
> [~asanso] 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}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
