[jira] [Commented] (SLING-7633) make Sling work without JCR locking

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482383#comment-16482383 ] 

Robert Munteanu commented on SLING-7633:
----------------------------------------

[~reschke] - I guess simplest for us would be to run the tests after OAK-7471 is implemented.

As for the checking the codebase, from the Oak commits we should be looking for:

* usages of {{mix:lockable}}
* invocations of {{LockManager}} methods addLockToken, removeLockToken, lock, unlock

Is that correct?

> make Sling work without JCR locking
> -----------------------------------
>
>                 Key: SLING-7633
>                 URL: https://issues.apache.org/jira/browse/SLING-7633
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>            Reporter: Julian Reschke
>            Priority: Major
>
> The Oak team is planning to phase out JCR locking (see <https://issues.apache.org/jira/browse/OAK-6421>). This means that at some point the repository will start to throw exceptions when trying to lock nodes, and the repository descriptors will say that locking is not supported.
> As part of <https://issues.apache.org/jira/browse/OAK-7458>, we have added logging for lock related calls (see org.apache.jackrabbit.oak.jcr.lock.LockDeprecation) so that we can identify callers.
> One early find was: 
> <https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentLoaderService.java#L321>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)